You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started with your ASP.Net identity sample, but I'm hosting the identity endpoint (Identity Server 3) in my ASP.NET (full framework). If I read it right, the login popup thinks it's time to close because the window's current URL matches the originating URL. Is this correct? Is this a limitation of aurelia-auth or is there an option somewhere to make it be more strict in its checking? E.g. don't look for http://localhost:1234, but look for a URL that's not http://localhost:1234/identity.
Or is it a really bad idea to host my identity system in my app? My app is the only thing that will use it. Or perhaps I shouldn't use the code auth flow and use the resource owner flow with a custom login page?
The text was updated successfully, but these errors were encountered:
I started with your ASP.Net identity sample, but I'm hosting the identity endpoint (Identity Server 3) in my ASP.NET (full framework). If I read it right, the login popup thinks it's time to close because the window's current URL matches the originating URL. Is this correct? Is this a limitation of aurelia-auth or is there an option somewhere to make it be more strict in its checking? E.g. don't look for http://localhost:1234, but look for a URL that's not http://localhost:1234/identity.
Or is it a really bad idea to host my identity system in my app? My app is the only thing that will use it. Or perhaps I shouldn't use the code auth flow and use the resource owner flow with a custom login page?
The text was updated successfully, but these errors were encountered: