***Note from Migration:***
Original Title was: Add support for integrated Windows Authentication (IWA)/ Single Sign On (SSO) for rest services (fmedatastreaming)
If you configure fmeserver for integrated Windows Authentication (IWA)/ Single Sign On (SSO), it affects the web UI only, not rest services (as far as I know). This enhancement will make it easier to access fmedatastreaming with published parameters etc. in a secure environment.
Hi
Why do I identify myself every time I use a service hosted by us internally.
Although I use AD integration to use FME .
Can someone give us instructions how to avoid irritation ?
Regards
Ahmed Jamasome time ago we requested support for Windows Authentication (IWA)/ Single Sign On (SSO) for rest services (fmedatastreaming). Nothing happens... It seems to me that hardly anyone is interested in secure and userfriendly rest- services?How can we get some action?
According to Safe support this feature is registered as Case-id: C120339
will PR#58971 be solved in fmeserver 2018?Is it possible that this will be fixed in FME Server 2018?
Is it possible that this will be fixed in FME Server 2019?
Please note that this has not been addressed for FME Server 2018 or FME Server 2019. We do not have this work committed to our plans at this time.
So, what can you do right now? We would love to gather information on the various use-cases and workflows that you need this capability implemented for. What endpoints are you using? Have you integrated them into a custom web application? How do your users access the service(s) that ultimately trigger a Job on FME Server?
If you are able to provide a short paragraph and post it as a comment here, or, especially if you have drawings, diagrams, or screenshots to share (or confidential information) – please send them via Safe Support (remember to reference this Idea thread).
We will need to make an informed decision, and having this information in-hand will be critical if we need to evaluate different technologies to replace what we have currently – for example, what if we determine migrating our REST API to a solution with a better backbone that can support SSO requirements is needed; we want to make sure it best fits the mould of your workflow.
This has not been resolved for FME Server 2018. Please see my comment from 16 May 2019 in the main thread. (Posted for visibility in case other users come across this specific comment.)
This has not been resolved for FME Server 2019. Please see my comment from 16 May 2019 in the main thread. (Posted for visibility in case other users come across this specific comment.)
This has not been resolved for FME Server 2018. Please see my comment from 16 May 2019 in the main thread. (Posted for visibility in case other users come across this specific comment.)
one possible solution is to add functionality to configured a workspace to run immediately without showing the parameter form by adding a optional parameter ‘runImmedaiately=true’.
Example GET request: https://fme.flow.com/fmeserver/streaming/fmedatastreaming/repository/works.fmw?param=123&runImmedaiately=true
Steps:
1. The user cliks on a predefines url.
2. The user is authorized by Azure Active Directory or Windows Active Directory.
3. The output is prodused and returned to the user immediately.