Hi, I am trying to run a series of transformations using the FME Rest API. Sometimes it works just fine, however, sometimes I get the message "Authentication failed: Failed to bind to Active Directory". (401). I created a token valid for 10 days and used a HTTPCaller to POST to the URL "http://ourserver:8080/fmerest/v2/notifications/topics/LDR_Trigger/message/raw?token=123456&detail;=low". Sometimes it looks like if I login to the FMEServer UI, it remembers the token and the result is as I expect. Has anyone any experience using FME Server REST service on Active Directory?
Page 1 / 1
Hi Helmoet,
I use the REST API with AD all the time and until now I did not have any problems with it.
Sounds to me more like a network issue that FME Server.
Cheers,
Itay
Hi @helmoet
This does appear to be a known issue, where the authentication fails after a period of non-usage.
One workaround - or at least a test to see if this really is the issue - is to set up a small job that runs every five minutes and polls the AD. Something like Creator > FMEServerJobSubmitter > Workspace in the Samples repository. Then FME will never be idle and the authentication problem won't occur.
That's for sure not a great solution, but I see this is scheduled to be fixed in FME2017.
If you carry out that test, and it shows that this idling is the problem, I suggest you contact our support team and give them the reference PR#71210. Then they will have your details and will be able to let you know when this is fixed - or any other workarounds they might have.
Apologies for any inconvenience this is causing,
Mark
Hi Helmoet,
I use the REST API with AD all the time and until now I did not have any problems with it.
Sounds to me more like a network issue that FME Server.
Cheers,
Itay
Hi, going to setup the @Mark2AtSafe test... Bit late, though.
At second hand, we don't want to enter user credentials to the system (since they change at relatively short periods). Hence we use the fme token to pass around that.
Please note that this issue has now been resolved for FME Server 2017 Build 17245 or newer! Active Directory has been completely rewritten for this release and we are confident the idle activity + authentication issue has been resolved.
Please contact Safe Support if you continue to experience any issues or unexpected behaviour.
Hi @RyanAtSafe,
I experimented on FME2017 Workbench. However that version FME(R) 2017.0.0.0 (20170207 - Build 17245 - WIN64) is not stable enough. Group by on bufferer transformer allways result in crash. Also Data Inspector crashes when turning off background image. And AWE reader for satellite data produces lot of red message however seems to run fine.
Hi @RyanAtSafe,
I experimented on FME2017 Workbench. However that version FME(R) 2017.0.0.0 (20170207 - Build 17245 - WIN64) is not stable enough. Group by on bufferer transformer allways result in crash. Also Data Inspector crashes when turning off background image. And AWE reader for satellite data produces lot of red message however seems to run fine.