Hello Community,
A client is using the WS Foundation authentication feature in their infrastructure. I know it is an old protocol and I would like to know how to integrate it into the OutSystems platform. I couldn't find anything specifically with this name. Is it possible to use this authentication method natively in OutSystems or do I need some Forge component. In this case, is there any other feature that is suitable for WS Foundation?
Excuse my ignorance, but I don't know much about this protocol. I didn't even find any documentation on the internet that was very clear.
Additional information:
Thanks.
Hello everyone!
Thanks for your help!
After getting some information from you and searching for some content, we created a component to support WS-Federation. As a great way to contribute to the community, I've made it available here on our Forge:
https://www.outsystems.com/forge/component-overview/22453/ws-federation-connector-o11
Once again, thank you all!
Are you sure about the name? Maybe they are using "WS-Federation"?https://en.wikipedia.org/wiki/WS-Federation
Hi Sérgio
Thanks for the correction, yes it is WS-Federation
I consulted Neo, but there is no support.
Has anyone implemented WS-Federation? Do you know where to start? Since I have limitations with the client's environment, I cannot access it directly to test authentication. I would need more precise information to adapt it to the client's infrastructure team and I can only provide the necessary support.
In this case, it could even be .NET code to help speed up the process.
You could of develop your own WS-FED authentication flow. At a glance this is basically
* Redirecting a user to the WS-FED authentication URL with wreply address
* Implement a REST Expose where the IdP can POST the WS-FED response (this is the wreply address)
* Validate the response, extract the SAML claims, lookup a corresponding user from the user entity or create a new one and finally use the (System) Login method to login the user
However I would not recommend building your own flow - and WS-FED is a pain in the a.. - for this outdated authentication protocol. especially as you write that in the future you are looking into ODC as well, which - as of now - only support OpenID connect compatible IdP. (If you want to go that route I recommend to use a WS-FED dotnet library for handling the message exchange, signing and validation.
My suggestion would be to use an Identity Broker (Entra, Keycloak, Okta asf). You would configure the Broker to federate with the WS-FED IdP and configure the broker in O11 (SAML) and ODC (OpenId Connect).
Best
Stefan