SAML SSO with Okta Fails #588
Unanswered
nikkisaildrone
asked this question in
0. General bugs and questions
Replies: 1 comment 2 replies
-
Hey @nikkisaildrone, there could be a few reasons for this SSO issue – maybe the 'audience restriction' URL in Okta isn't correct, or you didn't copy the certificate properly (it should start and end with '---BEGIN CERTIFICATE---' and '---END CERTIFICATE---'). To get to the bottom of this, we'd need a closer look at your SAML setup. Could you send us the details at [email protected]? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have a Pro Plan with Gitbook and our admins for Gitbook and our Okta org have followed the steps here to set up SAML SSO with our org's Okta account: https://docs.gitbook.com/account-management/sso-and-saml/saml#creating-end-user-account
I have confirmed that I have been added to our Okta org's Gitbook app. I should be able to sign on to the site with Okta, yet every time I attempt to do so I hit this error:

It looks like Gitbook is consistently trying to route through Google SSO for login despite our admins having set up Gitbook to use Okta SSO. Is this a bug? Anything we can do to rectify this?
Beta Was this translation helpful? Give feedback.
All reactions