Admin and User Operations

user management & role based access the floating server has two types of users 1\ administrators manage the server activate or deactivate licenses by adding or removing them from the floating server manage users who can register (check out) licenses 2\ management users managed by administrators can register/unregister to licenses added to the floating server can send license and feature consumption data back to the server, usually via a client application authentication by default, both admin and user actions require authentication if disableuserauth is set to false in the configuration file, only admin actions require authentication ; users can perform actions without logging in by default, both admin and user actions require authentication if disableuserauth is set to false in the configuration file, only admin actions require authentication; users can perform actions without logging in user setup admin adds each user to the server admin sets an initial password and shares it with the user on first login, the user must change their password via post /api/v5/auth/change password post /api/v5/auth/change password for a complete list of api calls for admins and users, refer to the swagger documentation administrator actions authentication required yes authentication required yes 1\ user mangement login post /api/v5/auth/login post /api/v5/auth/login add user post /api/v5/auth/add user post /api/v5/auth/add user remove user post /api/v5/auth/remove user post /api/v5/auth/remove user 2\ administrators online licenses add license post /api/v5/license post /api/v5/license remove license delete /api/v5/license/{id} delete /api/v5/license/{id} offline licenses generate offline activation request post /api/v5/license/offline/activation/generate post /api/v5/license/offline/activation/generate upload and activate license file post /api/v5/license/offline/activation/upload post /api/v5/license/offline/activation/upload generate offline deactivation request post/api/v5/license/offline/deactivation/generate post/api/v5/license/offline/deactivation/generate air gapped licenses generate activation code post /api/v5/license/airgap/generate post /api/v5/license/airgap/generate upload license file & confirmation code post /api/v5/license/airgap/activate post /api/v5/license/airgap/activate generate deactivation code post /api/v5/license/airgap/deactivate post /api/v5/license/airgap/deactivate deactivate using confirmation code post /api/v5/license/airgap/activate bundle management add bundle post /api/v5/bundle post /api/v5/bundle remove bundle delete /api/v5/bundle/{code} delete /api/v5/bundle/{code} admins can also perform all actions that users are allowed to do user actions authentication required authentication required yes (unless disableuserauth is false) register/unregister to licenses post /api/v5/license/{id}/user/register post /api/v5/license/{id}/user/unregister post /api/v5/license/{id}/user/register post /api/v5/license/{id}/user/unregister register/release features post /api/v5/license/{id}/feature/register post /api/v5/license/{id}/feature/release post /api/v5/license/{id}/feature/register post /api/v5/license/{id}/feature/release add license or feature consumption post /api/v5/license/{id}/consumption/add post /api/v5/license/{id}/consumption/feature/add post /api/v5/license/{id}/consumption/add post /api/v5/license/{id}/consumption/feature/add jwt authentication obtain a jwt token post /api/v5/auth/login post /api/v5/auth/login include the jwt in the authorization header for all authenticated requests authorization bearer \<your jwt token> authorization bearer \<your jwt token> example floating license flow admin creates a user user logs in and changes their password user logs in again to obtain a jwt admin adds the license post /api/v5/license post /api/v5/license user registers to the license post /api/v5/license/{id}/register post /api/v5/license/{id}/register