AAE-37746 Add front-channel logout route/component #11292
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alep85
changed the title
alep85
changed the title
alep85
force-pushed
the
fix/AAE-37746-single-logout
branch
3 times, most recently
from
4d71e26 to
2c10fea
Compare
alep85
requested review from
DenysVuika,
eromano and
popovicsandras
as code owners
alep85
force-pushed
the
fix/AAE-37746-single-logout
branch
from
4f75afd to
ff16cac
Compare
…l of issuer/session id from claims
…mponent logic to always logout the user
alep85
force-pushed
the
fix/AAE-37746-single-logout
branch
from
06d2bf4 to
8d8f4a0
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…l of issuer/session id from claims
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
https://hyland.atlassian.net/browse/AAE-37746
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: