In response to this sentence: Now that you have an Authorization Code, you must exchange it for an Access Token that can be used to call your API. Using the Authorization Code ( code ) from the previous step
Without knowing how you have implemented callback url it is hard to give more accurate suggestion but basically your callback url will be a server-side url that can receive a request with a code param that you can exchange for an accessToken.
I’m not sure if you have looked at our ASP .net Core 3.0 quickstart but I would highly recommend starting there to follow best practice for implementing Auth0 login Auth0 ASP.NET Core MVC SDK Quickstarts: Login
Thanks so much for your response. I have worked through the ASP .net Core 3.0 quickstart, but unfortunately I am restricted to using DotNet Framework 4.7.1 due to other application dependencies.
I have a fairly simple WPF application that needs to upload a file to my API. I have tested the functionality without authorization and that works fine.
"<"a href=“https://YOUR_DOMAIN/authorize?scope=appointments%20contacts&audience=appointments:api&response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=https://YOUR_APP/callback”>
Sign In
When I enter that using Chrome (or any other browser) where I am AUTHENTICATED it returns the code
(It has two returns a 200 ok and 302 found). I can manually read the code from this link.
In my code however, when I send the same URL the endpoint does not know I am authenticated. So I must be structuring the url request incorrectly or not including either the access_token or id_token.
Perhaps an example of how to structure this request in C# would be helpful.