libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

Fixing broken links after KC26 docs changes (#33577)

Browse source 
Closes #33576

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
Alexander Schwartz 2024-10-04 13:59:47 +02:00 committed by GitHub
parent 9fb187c222
commit d8c8c6a0be
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/documentation/release_notes/topics/19_0_0.adoc
View file

@ -92,4 +92,4 @@ See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kub
Starting with version 19, Keycloak supports sending logs using GELF to centralized logging solutions like ELK, EFK or Graylog out of the box. Starting with version 19, Keycloak supports sending logs using GELF to centralized logging solutions like ELK, EFK or Graylog out of the box.
You can find the documentation and examples to get you up and running quickly in the https://www.keycloak.org/server/logging#_centralized_logging_using_gelf[logging] {section}. You can find the documentation and examples to get you up and running quickly in the https://www.keycloak.org/server/logging[logging] {section}.

2
docs/documentation/upgrading/topics/changes/changes-19_0_0.adoc
View file

@ -67,7 +67,7 @@ For more information, see the https://www.keycloak.org/server/health[Health guid
As stated in the release notes, Keycloak now supports gelf logging for centralized logging systems out of the box. As stated in the release notes, Keycloak now supports gelf logging for centralized logging systems out of the box.
When you added the gelf related quarkus jars yourself in a prior version, make sure to switch to the supported configuration options in the https://www.keycloak.org/server/logging#_centralized_logging_using_gelf[logging guide] and remove your jars from the `providers` folder. When you added the gelf related quarkus jars yourself in a prior version, make sure to switch to the supported configuration options in the https://www.keycloak.org/server/logging[logging guide] and remove your jars from the `providers` folder.
= Changes affecting developers = Changes affecting developers

4
docs/documentation/upgrading/topics/changes/changes-22_0_0.adoc
View file

@ -215,7 +215,7 @@ This move is already reflected in our documentation and in our quickstart reposi
references for more information: references for more information:
* link:https://github.com/keycloak/keycloak-quickstarts[Keycloak Quickstart GitHub Repository] * link:https://github.com/keycloak/keycloak-quickstarts[Keycloak Quickstart GitHub Repository]
* link:https://www.keycloak.org/docs/latest/securing_apps/[Keycloak Securing Applications Documentation] * link:{securing_apps_link}[Keycloak Securing Applications Documentation]
We recommend starting to look into moving your applications to the alternatives from the references above. Those adapters should not be available anymore in future releases. We recommend starting to look into moving your applications to the alternatives from the references above. Those adapters should not be available anymore in future releases.
@ -228,7 +228,7 @@ The official adapter is now based on Jakarta and should be used as soon as you s
This change is already in our documentation and in our quickstart repository. For more information, please consider looking at the following references: This change is already in our documentation and in our quickstart repository. For more information, please consider looking at the following references:
* link:https://github.com/keycloak/keycloak-quickstarts[Keycloak Quickstart GitHub Repository] * link:https://github.com/keycloak/keycloak-quickstarts[Keycloak Quickstart GitHub Repository]
* link:https://www.keycloak.org/docs/latest/securing_apps/[Keycloak Securing Applications Documentation] * link:{securing_apps_link}[Keycloak Securing Applications Documentation]
If you cannot migrate your applications to Jakarta, you can still use the "legacy" SAML JEE adapter and still If you cannot migrate your applications to Jakarta, you can still use the "legacy" SAML JEE adapter and still
be able to integrate with future releases of the server. However, consider upgrading your applications as soon as possible be able to integrate with future releases of the server. However, consider upgrading your applications as soon as possible