4
Views
0
Comments
[Single Sign-On Mobile] Creating multi-tenant SSO in mobile app while adhering to current Best Practices
Question
single-sign-on-mobile
Mobile icon
Forge asset by OutSystems
Application Type
Mobile
Service Studio Version
11.55.79 (Build 65019)

Hello everyone!

I am aware of the current best practices for SSO login/logout, using Forge asset Single Sign On Mobile, as explained here: https://success.outsystems.com/documentation/11/user_management/end_users_authentication/configure_saml_2_0_authentication/updating_the_login_and_logout_flows_of_your_mobile_app_to_support_saml_2_0/

I am however under the impression that this action flow, as is, relies on Authentication being set to SAML 2.0 on /users, which does not support multi-tenant configuration. I am having trouble adapting this logic to work with multi tenant SSO configs (different suppliers) as, for example, asset IdP Mobile allows (including the configuration interface).

I tried to apply a SwitchTenant action in the beginning, along with my test Tenant site property UseSAMLAuthentication set to True, but regardless, I get the configuration for the generic Users Tenant.

I checked this other thread (https://www.outsystems.com/forums/discussion/78033/idp-idp-with-saml-for-multi-tenant-applications-and-group-synchronization-along/) where the community is using asset IdP. From some debugging on the Users Module, it appears that there is some of the same IdP logic inside some of the actions that are mentioned on the documentation (IdP_SSO_URL for example), but I'm still not understanding fully.


Apologies if this seems confusing. Thanks!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.