Auth0 OidcClient UWP SDK - 404 Not Found when trying to login

[calebq2010]

Currently we are trying to implement universal login with a UWP application using the Auth0.OidcClient.UWP SDK (v3.1.2) and referencing the quick start guide, and running into some issues with getting a 404 Not Found response back after hitting the auth0/authorize end point.

Here is the code that is called when clicking the login button in the application:

This is the code for displaying the result that is being returned:

The error message we are getting in loginResult.Error is NotFound and not really sure why this is happening. Below are some things to point out that we have noticed or tried:

1. We did confirm that we are being directed to the correct Application and Connection in Auth0

2. We did confirm that we have added the correct SID values in the Callback URL and Logout URL in the application per the quick start guide in Auth0 settings

3. The Auth0 application setup is using OIDC Conformant and the JWT signature algorithm is set to RS256

4. If we login with invalid credentials on the Universal login page we do get a log in Auth0 logs stating this BUT if we login with the correct credentials then no logs are showing in Auth0 logs for that event and NotFound is returned in the display results

5. We did attempt to use Fiddler to intercept the HTTPS calls but nothing more was shown besides the 404 Not Found error message we are seeing in loginResult.Error

6. We did find that we had to hard code the SID in the redirectUri value in order for it to send the correct callback URL to Auth0. If we did not hard code this value it was defaulting to a URL with the domain and /mobile at the end and not sure if this is by default or not.

[dan.woda]

Hi @calebq2010,

Welcome to the Community!

Can you do the following:

• Post the entire content of the error, typically there is a message that is more descriptive
• DM me your tenant name and I will look at your auth0 logs

Thanks,
Dan

[calebq2010]

Hey @dan.woda,

Thanks for your response! Unfortunately that is all the error information that I could find both in loginResult.Error and also using fiddler to see if I could get more error information.

I will DM you my tenant name and I am hopeful you can see more on your side for us.

Thanks,
Caleb

[dan.woda]

Great, thank you. I followed up there, and we will update this thread with relevant info.

[dan.woda]

Here is an update from our DM conversation:

What value for connection? A nonexistent connection is something that can throw a 404.

Interesting, yea I pass connection (which in this case we have a environment setup under my name of “exampleA”) into LoginAsync method:

Should this also be in clientOptions object or somewhere else?

Can you try omitting it completely and see if that works? It is optional so that will rule it out if we still get a 404.

If that solves it, then try in the client options and see if you still get it.

I removed the connection value out of LoginAsync and still received a 404 NotFound error. I did notice again that I got a log for successful logout in the Auth0 logs but I have been getting those before as well.
Also I will add if we do not pass the connection value of “exampleA” into LoginAsync then it defaults to our “exampleB” environment.

Could it be the clientID? Can you make sure it is properly entered as well?

Yea I triple checked that the clientID is correct and matches what is in the Auth0 application settings. I thought that originally as well.

[dan.woda]

From DMs:

They suggested trying this method of finding the redirect URI mentioned in the quickstart:

Alternatively - or if you have not associated your application with the Store yet - you can obtain the value by calling the Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri() method. So for example, in the OnLaunched method of your application, you can add the following line of code:

Auth0 Windows Universal App C# SDK Quickstarts: Login

Also they suggested trying this:

var client = new Auth0Client(new Auth0ClientOptions {
    Domain = "YOUR_AUTH0_DOMAIN",
    ClientId = "YOUR_AUTH0_CLIENT_ID",
    Scope = "openid offline_access",
    Browser = new WebAuthenticationBrokerBrowser(),
    RedirectUri = Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri()
});

@calebq2010

Morning Dan,

So I attempted both suggestions and it seems we still are getting a returned 404 error message back with no successful/failed logging in Auth0.

I did confirm that the Windows.Security.Authentication.Web.WebAuthenticationBroker.GetCurrentApplicationCallbackUri() is the correct URI that we were providing before hand so it was not wrong.

I did notice in the new client object that you suggested that the Browser was not mentioned in the walk through but actually pulls up a smaller/cleaner windows for the Auth0 login page which in my opinion looks better so thanks for that.

I am hopeful we can figure this out or have some more ideas on what to try.

Thanks,

Caleb

[dan.woda]

Finally solved this here:

@calebq2010

Hey Dan,

So I worked with another developer today and figured out what the issue was! It was an issue with how we use the security disclaimer on the universal lock screen and it required a value of skipSecurityDisclaimer (something my company build in custom for our clients nothing Auth0 does). In the application in Auth0 in advanced settings form application metadata we pass the value of skipSecurityDisclaimer: true and we are getting an access token back now with out issue.

The way we narrowed down that it was a 404: null/Security_Disclaimer was we had to take that request and open a browser and hit it in the browser which then pointed us to our issue.

I appreciate all of your help on this but I believe you can resolve this ticket.

Cheers,

Caleb