Fix the URL for initiating a JSConnect Sign In when using V3. #808
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.
This will close vanilla/support#1864
When we do not use JSConnect as the default method of signing in, we have the JSConnect button link directly to the endpoint that creates the JWT to be sent to the Authentication provider. When it is the default method, we don't do that. This causes inconsistencies in the way some customers have coded their applications to handle JSConnect.
This PR will make sure that all the links to sign in pass through the
/entry/jsconnect-redirectendpoint.Testing
/entry/jsconnect-redirect/entry/jsconnect-redirect/entry/jsconnect-redirect