Repository navigation
docs: say the realm registers the callback on the developer origin too - #10
Merged
Merged
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
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.
The comment on
KEYCLOAK_CALLBACK_PATHsaid the realm contract registers this path as the client's only redirect URI. The contract now also registers it on the developer originhttps://localhost:8443, where a developer runs a local BFF behind a web app's dev server, as Better Auth apps already do in development. The comment says so.Comment only. Nothing in the package's behavior changes, so there is no changeset and no release.
oxfmt --checkis clean.