6005503a3d
Previously, Keycloak did only support syncing groups from LDAP federation provider as top-level KC groups. This approach has some limitations: - If using multiple group mappers then there’s no way to isolate the KC groups synched by each group mapper. - If the option "Drop non-existing groups during sync” is activated then all KC groups (including the manually created ones) are deleted. - There’s no way to inherit roles from a parent KC group. This patch introduces support to specify a prefix for the resulting group path, which effectively serves as a namespace for a group. A path prefix can be specified via the newly introduced `Groups Path` config option on the mapper. This groups path defaults to `/` for top-level groups. This also enables to have multiple `group-ldap-mapper`'s which can manage groups within their own namespace. An `group-ldap-mapper` with a `Group Path` configured as `/Applications/App1` will only manage groups under that path. Other groups, either manually created or managed by other `group-ldap-mapper` are not affected. |
||
|---|---|---|
| .travis | ||
| adapters | ||
| authz | ||
| boms | ||
| common | ||
| core | ||
| dependencies | ||
| distribution | ||
| docs | ||
| examples | ||
| federation | ||
| integration | ||
| misc | ||
| model | ||
| quarkus | ||
| saml-core | ||
| saml-core-api | ||
| server-spi | ||
| server-spi-private | ||
| services | ||
| testsuite | ||
| themes | ||
| util | ||
| wildfly | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| ADOPTERS.md | ||
| CONTRIBUTING.md | ||
| get-version.sh | ||
| GOVERNANCE.md | ||
| LICENSE.txt | ||
| MAINTAINERS.md | ||
| maven-settings.xml | ||
| package-lock.json | ||
| pom.xml | ||
| prod-arguments.json | ||
| README.md | ||
| release.sh | ||
| SECURITY.md | ||
| set-version.sh | ||
| travis-run-tests.sh | ||
Keycloak
Keycloak is an Open Source Identity and Access Management solution for modern Applications and Services.
This repository contains the source code for the Keycloak Server, Java adapters and the JavaScript adapter.
Help and Documentation
- Documentation
- User Mailing List - Mailing list for help and general questions about Keycloak
- JIRA - Issue tracker for bugs and feature requests
Reporting Security Vulnerabilities
If you've 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 in our Issue Tracker. 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/standalone.[sh|bat]
Alternatively, you can use the Docker image by running:
docker run jboss/keycloak
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.
Other Keycloak Projects
- Keycloak - Keycloak Server and Java adapters
- Keycloak Documentation - Documentation for Keycloak
- Keycloak QuickStarts - QuickStarts for getting started with Keycloak
- Keycloak Containers - Container images for Keycloak
- Keycloak Gatekeeper - Proxy service to secure apps and services with Keycloak
- Keycloak Node.js Connect - Node.js adapter for Keycloak
- Keycloak Node.js Admin Client - Node.js library for Keycloak Admin REST API