Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport-4.0: deployment: Disable username validation for keycloak example #7230

Merged
merged 1 commit into from
Sep 6, 2023

Conversation

rhafer
Copy link
Contributor

@rhafer rhafer commented Sep 6, 2023

Set 'GRAPH_USERNAME_MATCH' to 'none'. To accept any username that is also valid for keycloak.

(cherry picked from commit 48306cb)

Copy link
Contributor

@mmattel mmattel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed 👍

@micbar
Copy link
Contributor

micbar commented Sep 6, 2023

file ../changelog/unreleased/fix-keycloak-example-username-validation.md: entry title does not have a prefix, example: Bugfix: restore old behavior

Set 'GRAPH_USERNAME_MATCH' to 'none'. To accept any username that is
also valid for keycloak.

(cherry picked from commit 48306cb)
@sonarcloud
Copy link

sonarcloud bot commented Sep 6, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@phil-davis phil-davis merged commit 9348f94 into owncloud:stable-4.0 Sep 6, 2023
2 checks passed
ownclouders pushed a commit that referenced this pull request Sep 6, 2023
Backport-4.0: deployment: Disable username validation for keycloak example
@rhafer rhafer deleted the backport/4.0/7226 branch September 6, 2023 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants