ASP.NET OWIN callbackURL "/signin-auth0" cannot be found

[mitWeb]

@jerrie1

If that cookie is set, it means the authentication flow is completed and the user should be signed in (the IsAuthenticated property should be true).

I just double checked and that cookie doesn’t get set in our project, even after it shows as login successful in Auth0 logs. Does this indicate that the Auth0 middleware isn’t picking up and setting User.Identity after a successful login? Is there anyway that I can try to debug why this is happening?

@jerrie1

As for the /signin-auth0 callback path, that is what we default to, but you can override it to whatever you want, e.g.

I thought that perhaps this was the hardwired into the Auth0 library to process the login and set the cookie and that changing it might break the flow. Good to get the confirmation that it doesn’t.

@jerrie1

If you do this, however, you will also need to configure your application in Auth0 to use that callback URL:

Yes, I am aware of that thank you. Auth0 is pretty good at displaying an error message when paths aren’t allowed. It’s the silent failing that’s a nightmare to debug!

@jerrie1

It may also be worth your while to ask on the ASP.NET forums. The Auth0 middleware is just a normal piece of OWIN authentication middleware, so this issue may not be related to Auth0 specifically, but to something else with regards to the OWIN middleware.

Thanks, I’ll post on their forums also.

@jerrie1

One thing I am unsure of is where the /bp path comes from in your app? Is that the path of your area?

Bp stands for business partners. The path was originally /business-partners but I changed it to /bp in case the hyphen was causing the path to be misunderstood somehow!

This is the area of the website that we want to hide behind the Auth0 login. It’s a kind of user area that allows setting of user preferences and posting product orders.

@jerrie1

maybe the area tries to resolve that URL and that is why you initially had the 404 when you set CallbackPath = new PathString(“/bp”)

The 404 occurs only with the default callback /signin-auth0. It redirects fine when the CallbackPath is set to a custom PathString.

@jerrie1

That is why I need to see a full sample app, otherwise it will be very difficult to track down the issue…

It’s mind boggling, why a copy of the project would redirect to the website root before any attempt at login! I’m lost as to what to try next.