I understand Bubble can integrate with Microsoft Active Directory Federation Services (MS-ADFS) to achieve single-sign on capabilities if OAuth2 is enabled.
I’m looking at exposing my app to a client company that users MS-ADFS.
Can someone describe (or point me in the direction of the doc that describes it) what the user experience would be in that case and what happens “under the hood”?
For example, for the user experience, I imagine that to access my app, users from the company with ADFS will point their browsers to my app’s URL and they will land “automagically” in a page of my app as if they had logged in using a special purpose screen in the app. Also, they would be identified as the Current User. Is that how it works from a user point of view?
What else happens under the covers?
To which page do they land? To the one pointed to in the URL or a to redirected one? And if the latter, where’s the logic to do that placed?
Since no one in this company has connected an app before using federated authentication (ADFS is very new, only installed to access Office 365), it may be good to have someone from Bubble help us do that. Is that help available?