Creating a new app with the Reactive Templates version 2.6.16 doesn't use SSO login anymore in the Login screen. No references are here anymore to the action "User_GetUnifiedLoginUrl" and the only action in Authentication -> GoLogin is "User_Login". Note that the Login action in the OnException and the UserInfo -> ClientLogin are still using the "User_GetUnifiedLoginUrl" action.
Please add this capability again and when doing so, please make it like in the Mobile Templates where it is detected if we have configured SSO or not.
As mentioned this always worked like this for Reactive Web apps on O11 and for the prerequisites mentioned here. The app template is a simple boilerplate for the developer to start developing so those scenarios are part of the developer's responsibility (as well as the the documentation provided to help and guide on achieving them) to implement any different flavour of any flow - a template should be as simple as possible to cover the most common use cases and help developers with less experience, so they don't get overwhelmed with a lot of code just by creating a new application.
Cheers,GM
Hello @Vincent Koning
Can you please elaborate a little bit more on what you're mentioning that is missing?The specific SSO flow only exists for Mobile and not Reactive Web where it's done through the exception handler. and you have multiple Forge components for this use case.Also, just looked at the version you mentioned is just like the way it used to be, with the same usage of User_GetUnifiedLoginUrl (even looked at version 1.4.8).
Hi Goncalo,
At the moment the templates doesn't seem to support SAML authentication in the flow on the Login screen. As of a few versions ago the Login screen flow used the User_GetUnifiedLoginUrl action to support this. In the latest version, this is no longer the case and only native Users authentication is used in the Login screen.
Feature documentation here: https://success.outsystems.com/documentation/11/developing_an_application/secure_the_application/end_users/end_users_authentication/configure_saml_2.0_authentication/updating_the_login_and_logout_flows_of_your_reactive_web_app_to_support_saml_2.0/
I hope this makes things more clear. If not please let me know.
Greetings,
Vincent
Hi @Vincent Koning
I believe there's some confusion here since the app templates for Reactive Web are working as expected and as they always were according to the prerequisites mentioned here.
Basically, the overall flow is:
Hope it helps clarify.
I understand the flow but I really thought that the login screen also supported this.
What would then be the correct handling of SAML authentication in the Login screen, if the Login screen was opened for whatever reason? If a new user lands on that page no OnException will be triggered but the user is also unable to successful login because that page doesn't support the correct flow.