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
In test, RackCAS's Fake CAS always seems to redirect back to CasAuthenticatableController#new, which always returns 401, which creates a loop. It does create the session correctly but after signing in with Fake CAS, you have to manually navigate back to your app.
Is it worth checking for an existing session in CasAuthenticatableController#new before returning 401?
The text was updated successfully, but these errors were encountered:
In test, RackCAS's Fake CAS always seems to redirect back to CasAuthenticatableController#new, which always returns 401, which creates a loop. It does create the session correctly but after signing in with Fake CAS, you have to manually navigate back to your app.
Is it worth checking for an existing session in CasAuthenticatableController#new before returning 401?
The text was updated successfully, but these errors were encountered: