<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
0D50Z00008G7UwBSAVOkta Classic EngineIntegrationsAnswered2018-08-23T20:28:07.000Z2017-02-10T04:43:21.000Z2018-08-23T20:28:07.000Z
.NET SDK AuthClient.Authenticate issue
It seems like calling AuthClient.Authenticate() changes the context of all API method calls to that of the user. So other API calls throw exceptions due to HTTP forbidden responses from the server.

  
  1.  var apikey = "somekey"; var env = "https://dev-999999.oktapreview.com"; var username = "user@company.com"; var pwd = "somepwd"; var oktaClient = new OktaClient(apikey, new Uri(env)); var authClient = oktaClient.GetAuthClient(); var result = authClient.Authenticate(username, pwd); //On 2nd try comment this out. There will be no exception var appClient = oktaClient.GetAppsClient(); var applist = appClient.GetList(); //throws exception if AuthClient.Authenticate() is called
 If this is by design, is there a way to do a user challenge without authenticating? My goal is challenge the user and then check if the user has access rights to the application. There's no way to do this if all calls subsequent to AuthClient.Authenticate() throw exceptions.


  • mike.davie1.5312945692819849E12 (Customer First Programs)

    Hello!

    This was resolved privately through a support case. If you have questions with a more complexity it's probably best just to file a ticket.

This question is closed.
Loading
.NET SDK AuthClient.Authenticate issue