Summary: None of your input or mathematical model data are shared with us when using WLS. The only information shared, is to validate your license and uniquely identify your container/machine. Read on to find out more.

Introduction

The "Web License Service" (WLS) is a mechanism for licensing Gurobi without binding that license to any particular machine. Instead, any process that needs to solve a Gurobi model will (automatically) connect to one of our servers to request a token. That token has a limited lifetime and will be refreshed automatically until it is no longer needed. WLS will track the number of concurrent tokens and limit that to the contractually agreed amount.

This article outlines the technical details of the request/response protocol for tokens and the data shared between you and Gurobi. For any questions, please reach out to your (technical) account manager.

Technical details

Each token request is a simple POST request over HTTPS to an endpoint at https://token.gurobi.com:443/ . This endpoint must be reachable from the machines or containers running Gurobi.

Documentation for the endpoint is available through our license portal once you're logged in. Requests contain the following information:

{
"licenseId": "xxxxxx",    // Your Gurobi license ID
"containerId": "79...0c", // Hashed unique identifier for your container/machine
"cores": 4,               // Number of physical cores
"version": "12.0.0",       // Gurobi version used
"duration": 5,            // Token lifetime in minutes (minimum 5)
"csEnabled": false,       // Whether Gurobi Compute Server is required
"csWorker": false,        // Whether Gurobi Remote Services Workers are required
"platform": "string",     // Operating system
"hostname": "string",     // Hostname of the container/machine
"tag": "string"           //
}

The response is a JSON Web Token.