<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
0D51Y00005xHKLpSAOOkta Classic EngineSingle Sign-OnAnswered2024-04-15T10:37:32.000Z2019-02-08T07:10:40.000Z2019-02-11T15:09:40.000Z

p653z (p653z) asked a question.

How to manage user operations of OKTA through .Net application using clientid & client secret key instead of using the API token key using Rest api

We are using OKTA Single Sign on to authorize user and use single sign on so for that purpose we are calling REST API by passing API key as Authorize token to perform user operations. So is their any way to create authentication token using clientid & client secret key instead of using the API token key using Rest api


  • The way to create authentication token using Client ID & Client Secret key is to install the Okta ADFS server.

    Many businesses are looking to implement a single sign-on so their users can easily access all of their cloud and web applications without authenticating to each application individually. 

    They conclude that the solution for single sign-on from Active Directory is Active Directory Federation Services.

    Expand Post
This question is closed.
Loading
How to manage user operations of OKTA through .Net application using clientid & client secret key instead of using the API token key using Rest api