0

I'm just looking at integrating OneLogin with my GSuite account and I want to get my head around the process a little better.

My goal is to allow the company users of my OneLogin app for Google Analytics to all launch and access it rather than everyone knowing the password.

OneLogin's documentation is a little bit...lacking in this department it would seem.

  1. I have my OneLogin account.
  2. I have set up a Google Analytics app (using SAML) on there.
  3. I've set the 'email' parameter to be that of my chosen analytics account that I want all users to access.

Over on Google Admin Console, I believe I need to set up SSO as it is currently not enabled.

I can see the headings:

Setup SSO with Google identity provider

Setup SSO with third party identity provider - am I right in thinking this is the one I need to fill out with the details from OneLogin?

Over on OneLogin I have values for:

  • Issuer URL
  • SAML 2.0 Endpoint (HTTP)
  • SLO Endpoint (HTTP)
  • ...and the Cert PEM file

Google asks for the following and I'm assuming the mapped values:

  • Sign In page URL (use OneLogin SAML 2.0 Endpoint?)
  • Sign Out page URL (use OneLogin SLO Endpoint?)
  • Change Password URL (skip this)
  • Verification Certificate (upload .PEM cert file?)

Am I on the right track here?

  • I only want to give access to Analytics and for the chosen login (email) but I'm assuming that OneLogin will handle all this when I set it up?

  • Will any other Google services be automatically affected by this change (e.g. Gmail, Drive etc....)

  • Will any 3rd party apps using Google Auth be affected?

Apologies for all the questions - first time setting this up and I want to make sure I do it right.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.