DevTest - Google SSO Configuration Guide
search cancel

DevTest - Google SSO Configuration Guide

book

Article ID: 278749

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

How to log in to DevTest 10.7.2 - IAM, Enterprise Dashboard, and Portal using Google Account ? 

This is what we intend to achieve at the end of following all the steps listed in this post. 

  1. An additional Button in the login screen of IAM/ED/Portal to let you log in using your Google account

  2. Pick any of your Google account already logged in the browser and access the product




    Notice that the user has been imported into IAM during the first login and provided access to Enterprise Dashboard.

    Since, the detailed steps to configure Okta with IAM were explained here, DevTest - OKTA SSO Configuration Guide. We will focus mostly 
    on the Google side configurations and some touchpoints on IAM side

Environment

DevTest 10.7.2

Resolution

Google Configuration with touching points in IAM Steps:

  1. Log into Google API Portal and define a credential
    https://console.cloud.google.com/apis

  2. Click on "Create Credentials" and choose "OAuth client ID" option


  3. Click on "Configure Consent Screen". The Consent screen is what will appear as you log in to Google to enter your application (Once everything is done).


  4. Choose External and Click Create


  5. In the following screen, define your application that wants to use Google Login.


  6. Fill out the app registration


  7. Save and close

  8. In the next section, select the scopes: email, profile, and openid, as shown below and save


  9. Save and continue to the next screen, where you choose some test users. Add some Gmail IDs that you want to allow access to the application.


  10. Save and continue. You are shown a summary of your consent screen.


  11. Go back to the Dashboard and click on "Credentials" from the left menu. On the right side, click on "Create Credentials"


  12. Choose "OAuth Client ID" and set the application type as "Web Application"

  13. Give a suitable name for the application. The most important field here is the Redirect URI. In order to get the proper value of the redirect URI we need to switch to IAM.


  14. Log into IAM and define a new OAuth/Oidc Provider. Let's call is googledemo, as an example. A redirect URI will show up. Copy it.


  15. Go back to Google Page and paste this Redirect URI with a slight tweak. Google is very strict about domains to use. Hence, tweak the hostname to have it as shown below:
    Instead of using this URI: https://hostname.local:51111/auth/realms/service_virtualization/broker/google/endpoint
    Make it as: https://hostname.example.domain.com:5111/auth/realms/service_virtualization/broker/google/endpoint 
    Where hostname.example.domain.com is the fully qualified host name of your server. Otherwise, Google will reject the URI.

  16. Click Create


  17. Your OAuth Client is created. From this screen, click on "Download JSON". We need some important values from the JSON to complete the configuration on the IAM side.

 

Additional Information

For Azure, see DevTest - Azure SSO Configuration Guide

For OKTA, see DevTest - OKTA SSO Configuration Guide