Open
Conversation
… url formula to handle this kind of cases
…perly to obtain the discovery configuration
tikurahul
requested changes
Aug 4, 2021
Author
|
Hi any update on this?? |
Author
|
Hi @tikurahul Do you have any further comments? |
|
Any chance this is going to be merged in? I'm running into this same issue trying to use this package with our Okta endpoint. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As stated in issue #188 , this resolves the need to parse correctly a given URL with query params as it is a valid option displayed in the Azure documentation for the discovery of the configuration of the issuer.