Data Director Implementation Guide

10.4 HotFix 1
- 10.5 HotFix 3
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Google Single Sign-On Login Provider Implementation Example

The Resource Kit contains a sample login provider implementation for Google Single Sign-On (SSO). The sample login provider implementation demonstrates one way of implementing SSO.

You can find the sample login provider implementation for Google SSO in the following file:

<MDM Hub installation directory>\hub\resourcekit\samples\sso\GoogleSSO\source\java\com\siperian\dsapp\sso\google\GoogleLoginProvider.java

When a user requests access to Informatica Data Director, the login provider authenticates the user through a sequence of events.

The following image shows the sequence of events that occurs when you implement Google SSO with the sample login provider implementation:

The Google Single Sign-On process flow from the initial user request to the granting or denial of access.

The following sequences can occur based on whether the user is logged into Informatica Data Director, logged in to Google, or not logged in to Informatica Data Director or Google:

Sequence for users that are logged in to Informatica Data Director.: When a user requests access to Informatica Data Director, the login provider checks to see whether the user is logged in. If the user is logged in to Informatica Data Director, the login provider grants access to Informatica Data Director.
Sequence for users who are not logged in to Informatica Data Director, but are logged in to Google.: When the login provider determines that the user is not logged in to Informatica Data Director, it checks if the user is logged in to Google. If the user is logged in to Google, the login provider passes the Google credentials of the user to the MDM Hub. The MDM Hub Security Providers tool authenticates the Google credentials. If the MDM Hub Security Providers tool authenticates the user, the user can access Informatica Data Director. If the Security Providers tool does not authenticate the user, the login provider redirects the user to the Google login page to enter different credentials.
Sequence for users who are not logged in to Informatica Data Director, and are not logged in to Google.: When the login provider determines that the user is not logged in to Informatica Data Director or Google, the login provider redirects the user to the Google login form. In the sample implementation, the login provider redirects to the Google login form instead of the Informatica Data Director login form because
isUseIDDLoginForm
is
false
. If you set
isUseIDDLoginForm
to
true
, the login provider redirects to the Informatica Data Director login form.; After the user logs in to Google, the process begins again, but the user is now logged in to Google. The MDM Hub Security Providers tool authenticates the Google credentials for the user.

Rename Saved Search

Table of Contents

Data Director Implementation Guide

Data Director Implementation Guide

Google Single Sign-On Login Provider Implementation Example

Google Single Sign-On Login Provider Implementation Example