In 2018 every user could only have one token, and this token would be assigned all of that users permissions, therefore using the generate token service, the only choice was to update or overwrite the existing token.

Instead in 2019 you have the ability to create multiple tokens per user and define permissions on an individual token basis for use with different applications/services. Therefore in order to update and existing token you will need to explicitly identify that token in the request, this can be done using the FME Server Rest API.

In FME Server if you view the Token Management page you'll see that using the https://<fmeserver>/fmetoken/generate URL generates a Session Token, session tokens will be assigned all the permissions that the User who created them has, these should be short-lived and really just be used by FME Server and for testing purposes. Instead for tokens being used by other applications you should be using API Tokens as their permissions can be restricted and tailored for specific use.

To create the API Token, this can be done either via the Web UI or through the Rest API POST /tokens endpoint (https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/tokens/createForm_post_1).

Every Token, API or Session, has a unique name, so once created you can use the PUT /tokens/<user>/<name> endpoint to update the existing Token (https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/tokens/updateForm_put_4).

Hi @hollyatsafe,

Great explanation, quite clear. Thank you.

I made a few screenshots of the Generate Token differences between 2018 and 2019:

FME Server 2018 WebInterface Manage Token:

FMEServer 2019:

And the link to the FME Server-Admin 2019 Token Management:

https://s3.amazonaws.com/gitbook/Server-Admin-2019/ServerAdmin4FMEServerUserAdministration/4.07.TokenManagement.html

I still have a question about the Tokens, as far I can see, Session are only used per user and per session in the FME Server Web Interface login and don't have other functionality, right?

In the Session Tokens list I see the Web Application Login, the FME Rest API (created from the Post /Tokens Try it out! in https://<fmeserver>/fmerest/apidoc/v3/#!/tokens/createJson_post_2 ) and Token Service Login created by https://<fmeserver>/fmetoken/generate.json?user=<user>&password=<password> are there other possibilities?

So in the Session Tokens you can just manage (Enable, Disable and Remove) the tokens in the list and the names in the list do not contain the token code, right?

Tanks again for explaining this new functionality.

Kind regards,

In 2018 every user could only have one token, and this token would be assigned all of that users permissions, therefore using the generate token service, the only choice was to update or overwrite the existing token.

Instead in 2019 you have the ability to create multiple tokens per user and define permissions on an individual token basis for use with different applications/services. Therefore in order to update and existing token you will need to explicitly identify that token in the request, this can be done using the FME Server Rest API.

In FME Server if you view the Token Management page you'll see that using the https://<fmeserver>/fmetoken/generate URL generates a Session Token, session tokens will be assigned all the permissions that the User who created them has, these should be short-lived and really just be used by FME Server and for testing purposes. Instead for tokens being used by other applications you should be using API Tokens as their permissions can be restricted and tailored for specific use.

To create the API Token, this can be done either via the Web UI or through the Rest API POST /tokens endpoint (https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/tokens/createForm_post_1).

Every Token, API or Session, has a unique name, so once created you can use the PUT /tokens/<user>/<name> endpoint to update the existing Token (https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/tokens/updateForm_put_4).