-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
11039 the api should return a 401 status code when a session is invalid #11658
11039 the api should return a 401 status code when a session is invalid #11658
Conversation
288d8e3
to
2033fcb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conceptually it is not ok to change the response code of the endpoint in the delegating handler that is used to call third-party service.
Just curious, when we're getting the invalid session? Seems like we're solving the issue for gitea session since solution lies in the delegating handler. Are we trying to solve the problem when user logs in from, for example 2 browsers?
…rom source control fetch remote changes method
416ee29
to
9168884
Compare
f873e70
to
1206f0f
Compare
backend/src/Designer/Services/Implementation/SourceControlLoggingDecorator.cs
Outdated
Show resolved
Hide resolved
91818f3
to
b602ab5
Compare
Description
Add a custom 401 delegation handler on the http client for the gitea service. The custom delegation handler checks if the response from the underlying gitea api is 401 when the appKeyToken is no longer valid and deletes all cookies.
Related Issue(s)
Verification