<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
0D54z0000AHYhfbCQDOkta Classic EngineAPI Access ManagementAnswered2024-11-21T16:27:42.000Z2024-11-20T13:41:47.000Z2024-11-21T16:27:42.000Z
The best way to organize multiple API management

So we have the next requirements:

We should connect Each new Okta organization that comes to us as a new Enterprise connection in Auth0. That allows our application to use the needed auth0 auth connection to users from different okta organizations, and we don't need to store any access creds/keys from okta, this job slides to auth0. - This part is not hard to build, and we already have a demo for that.

 

The main concern goes from the next part of the requirement

So, after the user logs in through auth0 > okta, we should get all applications from okta and show them in our UI...

As far as I know, there is no way to use somehow access tokens or code from auth0 to get something in Okta Api.

 

 

After I read the documentation, It's clear that we should use api key from each Okta organization in our backend and save those keys in our DB.

But this way is not secure, and I'm curious if there is any way to do this using a Custom Auth server? (like create one dev okta org and then in each new okta organization add our server as additional auth server)

Or is there another way we can manage not limited amount of incoming Customers that have okta organization?

 

 

 

 

 


  • DianaL.19788 (Customer Support Online Community and Social Care)

    Hello @User17321080216554304030 (Customer)​ , thank you for contacting Okta Community!

    I've reviewed our documentation for something relevant. It looks like your question is more appropriate for our dedicated Okta Developer Forum. I advise reaching out via devforum.okta.com  as they will have more insight into this topic. 

     

    While we'll do our best to answer your questions here, this medium is more inclined towards Okta's core products and features (non-developer work).

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
This question is closed.
Loading
The best way to organize multiple API management