Hi,
we generate some Topic's and get the POST URL. There is this fmetoken=......But after one day there is a new generated tokenvalue in the URL. Why happen that and how we avoid this for the future? We have some external application, which use this URL and are depends on a static FMEToken
thanks Jan
When you generate the token you can specify the duration of validity, from a few seconds up to two years. You'll probably want to use a custom API token for this particular use case.
For more information see https://docs.safe.com/fme/html/FME_Server_Documentation/WebUI/Manage-Token.htm
Hi David,
thanks for fast answer. If I make a custom API Token, then I get the token-value. But how I get or see the POST-URL with this Token-Value?
Hi David,
thanks for fast answer. If I make a custom API Token, then I get the token-value. But how I get or see the POST-URL with this Token-Value?
I'm not sure I understand. You'll have to modify your own POST request to use the dedicated token.
I'm not sure I understand. You'll have to modify your own POST request to use the dedicated token.
We have a arcgis quickcapture-app, which triggered via a Webhook (in this case the POST-URL "https://portal.ewp.ch/fmerest/v3/notifications/topics/../message/subscribercontent?fmetoken=96beae8181bee2c07326dcc393f4aba51ff77823") a published workspace. The way in FME Server to build up a Notificationprocess is simple. If we generate an API Token, it is for me not clear how to use this in a Webhook. With the way over the Notificationsprocess is that more clear and simple, but for us useless, when it changes the fmetoken automatically...