<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008KfdKaSAJOkta Classic EngineOkta Integration NetworkAnswered2024-04-15T11:18:59.000Z2018-09-05T23:06:20.000Z2018-09-06T22:32:54.000Z

cspvs (cspvs) asked a question.

September 5, 2018 at 11:06 PM
Has anyone been able to successfully integrate 1Password with Okta using the OP SCIM bridge?

I have it set up for our org, but Okta keeps telling me the credentials are invalid when I go to enable the integration. I know that the url for the scim bridge is correct and the bearer token is also correct. I've even tried re-generating the bearer token, but still no dice. I'm using a Docker file in our hosting environment. Any help or tips for getting this SCIM bridge working would be greatly appreciated.

  • 2 answers
  • 4.59K views
kro34 likes this.

  • o3qlr (o3qlr)

    Try using https://scim.example.com/scim as the Base URL. I was having the same problem. I contacted 1Password support and they suggested that. It worked and I asked them to update their docs, but it looks like they haven't yet. 

    Selected as Best

  • o3qlr (o3qlr)

    Try using https://scim.example.com/scim as the Base URL. I was having the same problem. I contacted 1Password support and they suggested that. It worked and I asked them to update their docs, but it looks like they haven't yet. 

    Selected as Best

  • cspvs (cspvs)

    Thanks so much, Andrew. Turns out I had two issues:

    1. I was using the incorrect Base URL (didn't have the /scim)
    2. My scimsession file actually did not exist in the directory on the server... I have a script that's running docker and that script is in a different directory from my scimsession file, so I guess it never actually initialized the session to properly authenticate with 1Password. I had to go into my app server and read the logs from there to determine there was an issue (I kept seeing incorrect bearer token errors which was a helpful hint that I'd screwed something up there).

     

    Solution:

    1. I added the /scim to my Base URL in Okta, as you suggested
    2. I copied the scimsession file to the same directory as my script that was running docker on the server

    I'm all set now with this issue that was partly due to my error and terrible documentation by 1Password (Okta's logging could've also been more useful instead of simply giving me the same generic authentication failure errors).

     

    Thanks again for your help!

    Joe

    Expand Post
This question is closed.
Loading
Has anyone been able to successfully integrate 1Password with Okta using the OP SCIM bridge?