I am trying to use the dotnet SDK to make API calls for user and group management. I’m hoping to take a proactive approach to prevent rate limiting, but the headers on the API calls that are made from the SDK are hidden from me.
I see a partial class with partial methods in the source. And the methods are mentioned in the migration guide. However, when I try to create my own partial class with the implementation for those methods I get the error that No defining declaration found for implementing declaration of partial method 'ApiClient.InterceptResponse(RestRequest, RestResponse)'.
Just to make sure, I decompiled the DLL from the NuGet package and looked at the ApiClient class and cannot find those methods there either.
Has anyone been able to successfully use those methods? Is there something I am missing, or an example of someone using those that I can follow?
My application is dotnet 8 using the latest version of the SDK (8.1.5).
Hi there, we will need to test this on our side too. You can use tools like Fiddler or Wireshark to look at the headers your API calls are making for your dotnet 8 application.
Have you used one of Okta sample applications and do you get the same error?
I would also suggest that you can open a support case with Okta support for assistance as well.
Maybe I’m looking in the wrong place. On the SDK page where there are sample apps, I don’t see any sample applications that use the Okta.Sdk.
If you show me where a sample application is I will download it and try it out.
Fiddler or Wireshark will help me to see what those headers are while running locally, but I’m hoping to have the application read the headers to see if I am getting close to the API limits and proactively slow down the API calls to avoid being rate-limited. So Fiddler and Wireshark won’t work for the application especially when deployed to production.