Forge

IdP Connector is a generic federated identity provider (IdP) connector, using the SAML protocol to connect to external identity providers. IdP allows your OutSystems applications to integrate with single sign-on (SSO) provided by most of the commercial Identity Provider companies. Also supports SSO from OutSystems mobile apps, alongside with IdP Mobile connector. Tested with Okta, Azure, ADFS, PingOne, OneLogin and ForgeRock OpenAM.

IdP Mobile connector allows an OutSystems mobile app to use the IdP connector component to authenticate and authorize an user, through the InAppBrowserEvents plugin. With this integration when the users access the OutSystems app, through the InAppBrowserEvents plugin they are redirected to a web page (known as the enterprise's login manager which should be prepared to be displayed in a mobile device) where they are prompted to enter their enterprise user name and password. Upon verification of the user’s login, the enterprise identity provider informs OutSystems server of the verified identity for the user who is logging in, and the user is redirected back to the app screens. No aditional configuration is needed in this plugin, since it uses the IdP connector and its configuration. A demo app is included to show how the plugin should be used and how it works. Tested with Okta, Azure, ADFS, PingOne and OneLogin

IdP Server is a generic federated identity provider (IdP). It allows to authenticate any user from a SP client.
<br>
With this component when the users access to a web portal with Single Sign-on from an SP client, they are redirected to a web page of this component (known as the enterprise's login manager) where they are prompted to enter their enterprise user name and password. Upon verification of the user’s cresentials, the component informs the SP client of the verified identity for the user who is logging in, and the user is redirected back to the end user portal website.
<br>
The IdP server supports SAML 2.0 protocol.<br>
Also supports APIs for authentication (though SAML 2.0 messages) for any mobile app (OutSystems mobile apps no longer requires InApp browser plugins alongside with this IdP server).
<br>
<br>
Tested with some SP clients like IdP connector and SimpleSAML<br>

Lifetime IdP Client module is a platform identity provider (IdP) client. It allows your OutSystems Platform applications such as Service Studio, Integration Studio, Service Center and Lifetime to integrate with most of the commercial IdP companies that support SAML 2.0 protocol for authentication purposes. With this integration when the OutSystems Platform users access the SAML Authentication module, they are redirected to a web page (known as the enterprise's login manager) where they are prompted to enter their enterprise username and password. Upon verification of the user’s credentials, the user is redirected back to the SAML Authentication module. The platform user is logged in, and a token is generated and presented on the screen so it can be used to access Service Studio, Integration Studio, Service Center and Lifetime. This component works in conjunction with the SAML Platform Authentication Plugin application also in the OutSystems Forge. For more information refer to the documentation in the SAML Platform Authentication application, more specifically on the Lifetime IdP Client module at http://LIFETIME_SERVER/LifetimeIdPClient

This component works in conjunction with the SAML Platform Authentication application, also in the OutSystems Forge. Lifetime IdP Client module is a platform identity provider (IdP) client. It allows your OutSystems Platform applications such as Service Studio, Integration Studio, Service Center and Lifetime to integrate with most of the commercial IdP companies that support SAML 2.0 protocol for authentication purposes. With this integration when the OutSystems Platform users access the SAML Authentication module, they are redirected to a web page (known as the enterprise's login manager) where they are prompted to enter their enterprise username and password. Upon verification of the user’s credentials, the user is redirected back to the SAML Authentication module. The platform user is logged in, and a token is generated and presented on the screen so it can be used to access Service Studio, Integration Studio, Service Center and Lifetime. The SAML Platform Authentication Plugin application must be installed in all the environments, including the Lifetime environment. For more information refer to the documentation present in the SAML Platform Authentication application, more specifically on the Lifetime IdP Client module at http://LIFETIME_SERVER/LifetimeIdPClient

Enables SSO between Reactive and Traditional Web applications

Gives you easy to use actions to generate the login URL and logout URL based on your application and auth server settings in Okta. Gives a function to be used in the authorization callback that Okta redirects you to after authenticating with them that validates your tokens. Also provides a login function that will log the user into Outsystems Users system using their Okta user id. To use the example effectively you will need to set up your Okta information in the Site Property settings like in the screenshot.

Use Microsoft MSAL to authenticate users in your application!