Yes, that is the name of the cookie which must be set, e.g
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).
As for the
/signin-auth0 callback path, that is what we default to, but you can override it to whatever you want, e.g.
var options = new Auth0AuthenticationOptions()
Domain = auth0Domain,
ClientId = auth0ClientId,
ClientSecret = auth0ClientSecret,
CallbackPath = new PathString("/a/b/c/whatever"),
If you do this, however, you will also need to configure your application in Auth0 to use that callback URL:
I am still a bit unsure however as to why this is happening.
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.
One thing I am unsure of is where the
/bp path comes from in your app? Is that the path of your area? If so then I am thinking that maybe when you set the
CallbackPath to a path also starting with
/bp/..., that maybe the area tries to resolve that URL and that is why you initially had the 404 when you set
CallbackPath = new PathString("/bp")
None of this however explains why it does not work when you leave the
CallbackPath as the default value. It should work… That is why I need to see a full sample app, otherwise it will be very difficult to track down the issue…