fix: invoking logout without credentials no longer throws error #37
Conversation
This file contains 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
jaredperreault-okta
force-pushed
the
jp-OKTA-436562
branch
from
3b501d5
to
7d287c0
Compare
jaredperreault-okta
force-pushed
the
jp-OKTA-436562
branch
from
7d287c0
to
8600c41
Compare
shuowu-okta
approved these changes
Nov 30, 2021
eng-prod-CI-bot-okta
pushed a commit
that referenced
this pull request
Nov 30, 2021
OKTA-436562 <<<Jenkins Check-In of Tested SHA: 25daa00 for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-oidc-middleware Files changed count: 3 PR Link: "#37"
Closed
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Invoking logout without valid credentials throws error
Issue Number: 436562
What is the new behavior?
401 is returned when logout is called without credentials
Does this PR introduce a breaking change?
Other information
Reviewers