Skip to main content
Question

How I can retrieve the CURRENT TOKEN via REST ?

  • April 19, 2016
  • 4 replies
  • 45 views

simonstefan
Contributor
Forum|alt.badge.img+2
How I can retrieve the CURRENT TOKEN via REST ?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

patrick_koning
Contributor
Forum|alt.badge.img+7

Something like this i believe.

FMEserver.generateToken( user, password, count, unit, callback) ,return String

see also

http://playground.fmeserver.com/getting-started/au...


simonstefan
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • April 21, 2016

Something like this i believe.

FMEserver.generateToken( user, password, count, unit, callback) ,return String

see also

http://playground.fmeserver.com/getting-started/au...

Hi,

Thank you for your answer.

What I need is to get the current token, not to generate a new one and use in other applications configuration files, applications which will use the token to deal with the FME server.

It is possible to find a workaround but it is much simpler for Jenkins to get the current token from the FME server and automatically configure and deploy the rest of applications.

If I generate a new token, other machines will be able to use the old token?

Thanks,


david_r
Celebrity
  • April 21, 2016

Hi

can use the lookupToken() method:

FMEServer.lookupToken( user, password, callback ) , return Object

See also the documentation here.

David


patrick_koning
Contributor
Forum|alt.badge.img+7

Hi,

Thank you for your answer.

What I need is to get the current token, not to generate a new one and use in other applications configuration files, applications which will use the token to deal with the FME server.

It is possible to find a workaround but it is much simpler for Jenkins to get the current token from the FME server and automatically configure and deploy the rest of applications.

If I generate a new token, other machines will be able to use the old token?

Thanks,

@simonstefan When a token for that user is already given out and still active you will be given back the same token. So it schould be the current one for that user.