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
This package works great on it's own. Even when I've pulled the few files into my own project and used the same appsettings locally it works fine. However, it doesn't against the client's MS OIDC system. Looking into it I'm trying to understand why a redirect_uri of https://mydomain/signin-oidc is generated when there isn't such a page in the solution nor Umbraco. Running locally, it all just works, you see the page that was protected. Running live, I'm redirected to mysite/signin-oidc which we don't have of course and so get a 404.
Just looking for some insight really to help debug. It would appear the client's system isn't respecting the return url.
The text was updated successfully, but these errors were encountered:
Turns out OAuth and OIDC are complicated beasts with several flavours of each. I eventually got it all working but required a lot of reading and viewing of tutorials, and that was just to work out what was at the client's end. No fault of the package, which was a great starting point. Once I knew what was actually at the client's end and slight adjustments made, it worked fine.
B2C Auth ain't for the faint-hearted! lol
This package works great on it's own. Even when I've pulled the few files into my own project and used the same appsettings locally it works fine. However, it doesn't against the client's MS OIDC system. Looking into it I'm trying to understand why a redirect_uri of https://mydomain/signin-oidc is generated when there isn't such a page in the solution nor Umbraco. Running locally, it all just works, you see the page that was protected. Running live, I'm redirected to mysite/signin-oidc which we don't have of course and so get a 404.
Just looking for some insight really to help debug. It would appear the client's system isn't respecting the return url.
The text was updated successfully, but these errors were encountered: