d28adcb81b
* Avoid NPE if realm configuration contains invalid required action configuration If users removed implementations or renamed the provider id of a required action, then the realm configuration might contain dangling references to required actions. If we then try to find the RequiredActionFactory to determine the if the required action is configurable then NPE is thrown. This PR prevents the NPE with a guard clause. Fixes #32624 Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com> * Log a warning if required action with missing provider is detected. Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com> --------- Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com> |
||
|---|---|---|
| .github | ||
| .idea | ||
| .mvn | ||
| adapters | ||
| authz | ||
| boms | ||
| common | ||
| core | ||
| crypto | ||
| dependencies | ||
| distribution | ||
| docs | ||
| federation | ||
| integration | ||
| js | ||
| misc | ||
| model | ||
| operator | ||
| quarkus | ||
| rest | ||
| saml-core | ||
| saml-core-api | ||
| server-spi | ||
| server-spi-private | ||
| services | ||
| test-framework | ||
| test-poc | ||
| testsuite | ||
| themes | ||
| util | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitleaks.toml | ||
| ADOPTERS.md | ||
| CONTRIBUTING.md | ||
| eslint.config.js | ||
| get-version.sh | ||
| GOVERNANCE.md | ||
| LICENSE.txt | ||
| MAINTAINERS.md | ||
| maven-settings.xml | ||
| mvnw | ||
| mvnw.cmd | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| pom.xml | ||
| PR-CHECKLIST.md | ||
| README.md | ||
| SECURITY-INSIGHTS.yml | ||
| set-version.sh | ||
| tsconfig.eslint.json | ||
| tsconfig.json | ||
Open Source Identity and Access Management
Add authentication to applications and secure services with minimum effort. No need to deal with storing users or authenticating users.
Keycloak provides user federation, strong authentication, user management, fine-grained authorization, and more.
Help and Documentation
- Documentation
- User Mailing List - Mailing list for help and general questions about Keycloak
Reporting Security Vulnerabilities
If you have found a security vulnerability, please look at the instructions on how to properly report it.
Reporting an issue
If you believe you have discovered a defect in Keycloak, please open an issue. Please remember to provide a good summary, description as well as steps to reproduce the issue.
Getting started
To run Keycloak, download the distribution from our website. Unzip and run:
bin/kc.[sh|bat] start-dev
Alternatively, you can use the Docker image by running:
docker run quay.io/keycloak/keycloak start-dev
For more details refer to the Keycloak Documentation.
Building from Source
To build from source, refer to the building and working with the code base guide.
Testing
To run tests, refer to the running tests guide.
Writing Tests
To write tests, refer to the writing tests guide.
Contributing
Before contributing to Keycloak, please read our contributing guidelines. Participation in the Keycloak project is governed by the CNCF Code of Conduct.
Other Keycloak Projects
- Keycloak - Keycloak Server and Java adapters
- Keycloak QuickStarts - QuickStarts for getting started with Keycloak
- Keycloak Node.js Connect - Node.js adapter for Keycloak