<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
0D54z00009xSaEcCAKOkta Classic EngineAPI Access ManagementAnswered2024-02-02T23:33:22.000Z2024-02-02T14:31:30.000Z2024-02-02T23:33:22.000Z

RyanB.56256 (Customer) asked a question.

ClientID Config/ API

I had to create a simple API for a vendor to call.

I followed this guide.

 

https://developer.okta.com/blog/2019/03/13/build-rest-api-with-aspnet-web-api

 

However, I noticed that 1 of our other clientID/Secrets tokens will work against my new API and vice versa.

 

Is there a way for me to limit this new ClientID/Secret to only have access to my new API? I haven't really done much with Okta so I have been googling my way through.

 

Thanks!


  • Mihai N. (Okta, Inc.)

    Hi @RyanB.56256 (Customer)​  , Thank you for reaching out to the Okta Community! 

     

     This question is more appropriate for our dedicated Okta Developer Forum.

    My advice would be to reach out devforum.okta.com to take advantage of their expertise.  

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

     

    Regards.

     

    --------------------------------

    Subscribe Today: The Okta Community is on YouTube

    Expand Post
This question is closed.
Loading
ClientID Config/ API