When using FME Workbench 2017.1 for connecting to FME server 2017.1 (purpose of downloading published workspaces), using
the saved WEB Connection entry (user credentials of a local FME server
user) – sometimes – the FME server without notice resets the User
created token.
FME server has LDAP and local FME authorisation.
Why is this happening?
Hi @martin,
As a first thought, it may be worth checking the TOKEN_REFRESH_INTERVAL parameter to see if this interval aligns with the times you have noticed the token refreshing.
Hi @martin,
As a first thought, it may be worth checking the TOKEN_REFRESH_INTERVAL parameter to see if this interval aligns with the times you have noticed the token refreshing.
Token was
create for interval of 2 years and TOKEN_REFRESH_INTERVAL parameter is ok. It
only happen when using FME Workbench 2017.1 for connecting to FME server 2017.1,
using the saved WEB Connection entry and not every time. Does that mean that when
using token you should not use login and password of that token in FME workbench?
Token was
create for interval of 2 years and TOKEN_REFRESH_INTERVAL parameter is ok. It
only happen when using FME Workbench 2017.1 for connecting to FME server 2017.1,
using the saved WEB Connection entry and not every time. Does that mean that when
using token you should not use login and password of that token in FME workbench?
You should be able to freely use a token and continue to login with username / password. Perhaps if you are using the token in a web application, for example, then consider creating a user account for that purpose specifically. Hopefully that will avoid this obvious inconvenience!
You should be able to freely use a token and continue to login with username / password. Perhaps if you are using the token in a web application, for example, then consider creating a user account for that purpose specifically. Hopefully that will avoid this obvious inconvenience!
Hey,
I had the same problem with my API Token in combination with FME server version 18305 (in FME Cloud) in combination with desktop 18312. Token expired after adding it to the web connections.
I needed the connection for the FMEServerJobSubmitter
Hey,
I had the same problem with my API Token in combination with FME server version 18305 (in FME Cloud) in combination with desktop 18312. Token expired after adding it to the web connections.
I needed the connection for the FMEServerJobSubmitter
@JeroenR - Our development team has been working on addressing the experience related to tokens in FME Server. In the current 2019.0 beta builds we enable the user to create multiple API Tokens that are separated from "Login / Session" tokens and the FMEServerWizards/Transformers in FME Desktop.
This separation should prevent unexpected behaviour related to token resets or expiration.