1

Closed

Minor Version Change Requires Switching Out All SSO-related Aplications

description

Perhaps not a direct issue, but we implemented an OWIN-based authentication component (with AD and Claims) and have many applications consuming the resulting token. When we recently upgraded from 3.0.0.0 to 3.0.1.0, we had to update each an every application (in-cycle or not) and push them all out. It was such a mess using the existing pattern. I understand that in order for the security tokens to be understood, that both sides of the "puzzle" must match. But that's the rub... Could you point us to a best practice whereas we could use a OWIN-based component that is "dropped" in or easier to replace. Right now the startup.auth and such are "embedded" in each project. Thanks!
Closed Mar 2 at 9:49 PM by mgirgin
The repo has moved to https://github.com/aspnet/AspNetKatana.

If you have questions, please file them there.

comments