<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
0D50Z00008G7VRJSA3Okta Classic EngineLifecycle ManagementAnswered2025-05-19T07:36:18.000Z2016-11-01T18:38:52.000Z2018-02-23T18:52:19.000Z
  • j5v7c (j5v7c)

    Hi Mohit,

     

    If you're looking at the SCIM endpoint to create users, you'll find the correct information at http://developer.okta.com/standards/SCIM/#create-account-post-users, but the base SCIM url is https://devXXXX.oktapreview.com/scim/v2, not /api/v1.

     

    What do you hope of achieving by importing the Okta certificates? If you are building your SCIM as an OAuth 2.0-based app (cf. http://developer.okta.com/standards/SCIM/#authentication) then our openID Connect configuration endpoint (http://developer.okta.com/docs/api/resources/oidc.html#openid-connect-discovery-document) and especially the jwks_uri value that gives you access to the keys available for your SCIM app.

     

    I hope this helps!

     

    Raphael.
    Expand Post
  • joel.franusic (Presales - Americas Strategic &amp;amp;amp;amp; Public Sector, Architects &amp;a)

    If you want to receive SCIM messages from Okta (where Okta is the "client" sending messages to a "server"), then Okta you will need to configure Okta, or the Okta On-Premise Provisioning (OPP) client with the base URL for your SCIM server.

     

    Okta does not support receiving SCIM messages sent to Okta (where Okta is the "server" and your code is the "client"). If you want to provision users inside of an Okta org, you will need to use the Users API.

     

    In either of these scenarios, the HTTP endpoints would need to be protected with SSL certificates signed by a trusted root certifacte authority.

    Expand Post
This question is closed.
Loading
scim