Google Apps as IDP (Identity Provider) solution by miniOrange helps you to SSO login to your applications/websites using Google Credentials. Google Apps Single Sign-On solution can be implemented by configuring Google Apps as SAML IDP in miniOrange, where miniOrange will act as SP. Here we will go through a step-by-step guide to configure SSO login between website/application and Google Apps by considering Google Apps as IdP (Identity provider) and miniOrange as SP(Service provider).
miniOrange also acts as an identity broker for cross protocol authentication. It basically means configuring a Service Provider following a particular protocol with an Identity Provider following some different protocol like SAML,OAuth etc. Once configured successfully you will be ready to securely access your website/application using Google Apps as IDP.
Mentioned below are steps to configure Google Apps as IDP via SAML and OAuth configuration. Follow the steps accordingly based on your requirement (SAML or OAuth).
Follow the steps to configure Google Apps as IdP by SAML configuration.
|Domain Mapping||Can be used to redirect specific domain user to specific IDP|
|Show IdP to Users||Enable this if you want to show this IDP to all users during Login|
|Send Configured Attributes||Enabling this would allow you to add attributes to be sent from IDP|
|Entity ID||Entity ID or Issuer|
|ACS URL (Assertion Consumer Service URL)||ACS URL|
Follow the steps to configure Google Apps as IdP by OAuth configuration.
|IdP Name||Custom Provider|
|IdP Display Name||Choose appropriate Name|
|OAuth Authorize Endpoint||From step 2||OAuth Access Token Endpoint||From step 2||OAuth Get User Info Endpoint (optional)||-|
|Client ID||From step 2|
|Client secret||From step 2|
|Service Provider Name||Choose appropriate name according to your choice|
|SP Entity ID or Issuer||Your Application Entity ID|
|ACS URL X.509 Certificate (optional)||Your Application Assertion Consumer Service URL|
|NameID Format||Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress|
|Client Name||Add appropriate Name|
|Redirect URL||Get the Redirect-URL from your OAuth Client|
|Descrption||Add if required|
|Policy Name||As per your Choice|
Note: Choose the Authorization Endpoint according to the identity source you configure.
In case you are setting up SSO with Mobile Applications where you can't create an endpoint for Redirect or Callback URL, use below URL.
You have a choice to set multiple IDPS for Single Application, i.e integrate multiple IDP and users can select IDP accordingly from which they want to authenticate themselves. There are three different ways to authenticate users using IDP.
Note : At once you can select either of them.
Few usecases where customers configure multiple IDPs -
|For Cloud IDP -||https://login.xecurify.com/moas/discovery?customerId=<customer_id>|
|For On-Premise IDP -||https://yourdomain.com/discovery?customerId=<customer_id>|
You can see the screenshot below of the IDP Selection Page with a list of IDPs .
Note: To view the IDP in drop-down list, go to Identity Providers tab > against your configured IDP > Select >Edit , here Enable the Show IdP to Users option.
If you have multiple IDPs and you want a certain set of users to authenticate from one IdP whereas another set of users to authenticate from another IdP, based on their email domains you can achieve this by using the following steps:- Our domain mapping feature
Lets say, there are two organisations under ADFS. One want to authenticate the users under the domain demo.com and other one with the domain example.com. For reference, We have taken the 2 organisations as two different IDPs and WordPress as SP. Follow the guides to set up ADFS and WordPress at your end.
If you have multiple IDPs (identity provider) and you want a certain application user to authenticate with one IDP and other application users with another IDP then you can achieve this by our Identity Source Feature.
Need Help? We are right here!