c315762883
* Allow host:port syntax for --debug in kc.sh Loosen the --debug argument parsing in kc.sh to accept full host:port addresses (e.g. 0.0.0.0:8787 or *:8787) in addition to plain port numbers. This enables JDWP to bind to all container interfaces when running Keycloak in Docker, without requiring manual JAVA_OPTS overrides or script edits. Closes #38924 Signed-off-by: mircea.talu <talumircea13@gmail.com> * Handle IPv6 address in --debug parameter in kc.sh Signed-off-by: mircea.talu <talumircea13@gmail.com> * Handle both bare and bracketed IPv6 addresses in kc.sh --debug parameter Signed-off-by: mircea.talu <talumircea13@gmail.com> * Handle corner cases in kc.sh --debug parameter IPv6 address handling Signed-off-by: mircea.talu <talumircea13@gmail.com> * Simplify kc.sh --debug parameter parsing, assume bracketed IPv6 addresses Signed-off-by: mircea.talu <talumircea13@gmail.com> * Remove final else case to avoid consuming following parameters Signed-off-by: mircea.talu <talumircea13@gmail.com> * Standardize indentation in kc.bat script Signed-off-by: mircea.talu <talumircea13@gmail.com> * Allow host:port syntax for --debug in kc.bat Signed-off-by: mircea.talu <talumircea13@gmail.com> * Add documentation for host:port usage in --debug parameter Signed-off-by: mircea.talu <talumircea13@gmail.com> --------- Signed-off-by: mircea.talu <talumircea13@gmail.com> Co-authored-by: Martin Bartoš <mabartos@redhat.com>
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
- Join #keycloak for general questions, or #keycloak-dev on Slack for design and development discussions, by creating an account at https://slack.cncf.io/.
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.
Joining a community meeting is a great way to get involved and help shape the future of Keycloak.
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