docs: add OIDC callback URL and external provider configuration notes#1451
Open
elyerr wants to merge 1 commit into
Open
docs: add OIDC callback URL and external provider configuration notes#1451elyerr wants to merge 1 commit into
elyerr wants to merge 1 commit into
Conversation
Signed-off-by: Elvis Yerel Roman <yerel9212@yahoo.es>
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
1 participant
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.
🤖 AI (if applicable)
Summary
This PR improves the documentation for OpenID Connect integrations by documenting a few configuration requirements that may not be immediately obvious during the initial setup.
Changes
Added documentation for the callback URL used by
user_oidc:Added notes about the
allow_local_remote_serversconfiguration option, which may be required when connecting Nextcloud to an external Identity Provider.Added notes regarding
trusted_domains, as some deployments require the Identity Provider domain to be trusted in order to avoid connectivity or authentication issues.Motivation
While testing integrations with external OpenID Connect providers, I found that these requirements are easy to overlook and can lead to authentication failures even when the provider configuration appears correct.
Documenting these details should help administrators complete the setup process more smoothly and reduce troubleshooting time.
AI Disclosure
The documentation text included in this PR was partially assisted by AI for wording and formatting purposes. All technical findings, validation, testing, and documentation content were reviewed and verified before submission.