Using the Floating Server

the v2 of the floating server is currently in an open beta please submit any bugs or feedback via our support tickets as we are actively working to resolve them to move to an initial public release in a timely manner user management & role based access there are 2 user types that interact directly with the floating server administrators , manage the server, can activate or deactivate licenses by adding or removing them from the floating server, and manage users who can register (check out) to a license management users managed by the admins, a user can check out (or "register / unregister") to a license that has been added to the floating server, as well as send license and feature consumption data back to the server—typically via a client application by default, both admin and user actions require authentication however, if you set the disableuserauth value to false in the configuration file, authentication is required only for admin actions all other actions can be performed without authentication each user is added to the server by an admin the admin sets an initial password and shares it with the user upon first login, the user is required to change their password using the api endpoint for a full reference of the api calls that can be made by administrators and users, please refer to the swagger page actions that can be performed by an administrator log in to the floating server add new user to the floating server remove user adding and removing license, online, offline and air gapped adding and removing bundles and every action that non admin users can do actions that can be performed by a user once they have been added by an admin, a user can perform the following actions register and unregister to licenses and floating features add license and feature consumption a more comprehensive reference for all available endpoints and their functionality is accessible via the swagger documentation page hosted on the server instructions on how to access it are provided later in this document jwt authentication every admin or user must obtain a jwt token via include this jwt in the authorization header of all requests that require authentication example floating license flow here’s a typical workflow for registering a user to a floating license admin creates the user user logs in and changes their password user logs in again to obtain a jwt admin adds the license via user registers to that license via using the swagger page below is an example using the add license endpoint on the swagger interface fill out the required fields in the request body and click execute if everything is correct, you will receive the appropriate response important look for the small lock icon 🔒 (or authorization icon) on the right side of the endpoint click this icon to provide your jwt token make sure to paste your token with the bearer prefix using cli instead of swagger once you’ve tested the request in swagger, you can easily switch to using the command line to do so, copy the equivalent curl command generated by swagger (you’ll see it below the response section)