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 other places where we link to services we include the sessionId so that it works. How is getting the HTML for the login screen as a response and not getting the chance to actually login not a bug?
We explicit required that the DIG session was different from the normal user session.
What do you mean?
@kgrgreer It used to be this way - where once logged in, you had DIG access. But we changed it, but having trouble remembering why. I recall something about on logout of the user, the DIG session was not logged out. So that's why I say it isn't a bug as we explicitly did this - just can't remember why. But if we address whatever the real session issue was, then I'm fine with using the user session.
Returns login screen HTML instead. Should send session with request.
FYI: @nanoscott
The text was updated successfully, but these errors were encountered: