Try Now

Web

4.3

(32 ratings)

0 reviews

1287

Rui Barbosa

Created on 29 August 2014

Details

IdP Connector is a generic federated identity provider (IdP) connector, i.e., the IdP Connector its an IdP Service Provider (it uses SAML as a protocol) It allows your OutSystems applications to integrate with single sign-on (SSO) provided by most of the commercial IdP companies. With this integration when the users access an OutSystems application, they are redirected to a web page (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 login, the enterprise identity provider informs OutSystems application of the verified identity for the user who is logging in, and the user is redirected back to the portal website. Also supports SSO from OutSystems mobile apps, alongside with IdP Mobile connector. Note: Tested with Okta, Azure, ADFS, PingOne and OneLogin.

Configure your application to use IdP Connector

As soon as you download this component you'll have a webpage (https://<your serer>/IdP/Instructions.aspx) with the detailed instructions on how to use configure your app to use IdP Connector.

Feature List

SAML Response validation
SAML decrypt assertion
Create SAML Request
The browser interacts with the user's SAML 2.0-compliant Identity Provider, validates the user credentials, creates the SAML assertion, and sends the assertion to OutSystems applications.
SSO lets users sign in once and remain authenticated as they access services in the circle of trust.
SAML Single-Logout flow (SLO initiated by IdP Connector or initiated by IdP Server)
Import/Export SAML metadata
Mobile Support (with IdP Mobile connector)

What’s new (4.1.0)

IdPMobile: added support to allow an user to Login and Logout from mobile apps through the system browser (in addition of InApp browser)
Configuration screen split into basic/advanced configuration, for newbies and advanced users respectively.
Displaying of certificate expire date
More user friendly error messages for some specific errors/scenarios (technical error is still being logged)
Bugfix: If Destination attribute was not present on the LoginResponse SAML message, an error was thrown
Bugfix: in some scenarios when receiving a LogoutResponse message, the SAML Issuer was not being retrieved from the message.

Reviews (0)

Tags

Support Options

This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from Rui Barbosa who created this component.

Dependencies