Fix documentation link to quickstarts to point to 'main' branch instead of 'latest' branch

closes #39798

Signed-off-by: mposolda <mposolda@gmail.com>
This commit is contained in:
mposolda
2025-05-19 10:15:26 +02:00
committed by Marek Posolda
parent 175102d03d
commit fe2790a09d
4 changed files with 8 additions and 8 deletions

View File

@@ -4,7 +4,7 @@
For certain applications, you can look at the following resources to quickly
get started with {project_name} Authorization Services:
* {quickstartRepo_link}/tree/latest/jakarta/servlet-authz-client[Securing a JakartaEE Application in Wildfly]
* {quickstartRepo_link}/tree/latest/spring/rest-authz-resource-server[Securing a Spring Boot Application]
* {quickstartRepo_link}/tree/main/jakarta/servlet-authz-client[Securing a JakartaEE Application in Wildfly]
* {quickstartRepo_link}/tree/main/spring/rest-authz-resource-server[Securing a Spring Boot Application]
* link:https://quarkus.io/guides/security-keycloak-authorization[Securing Quarkus Applications]
* link:https://www.keycloak.org/securing-apps/nodejs-adapter[Keycloak Node.js adapter]

View File

@@ -19,10 +19,10 @@ There are two sample projects in link:{quickstartRepo_link}[{quickstartRepo_name
|===
|Name |Description
| {quickstartRepo_link}/tree/latest/extension/user-storage-jpa[user-storage-jpa]
| {quickstartRepo_link}/tree/main/extension/user-storage-jpa[user-storage-jpa]
| Demonstrates implementing a user storage provider using JPA.
| {quickstartRepo_link}/tree/latest/extension/user-storage-simple[user-storage-simple]
| {quickstartRepo_link}/tree/main/extension/user-storage-simple[user-storage-simple]
| Demonstrates implementing a user storage provider using a simple properties file that contains username/password key pairs.
|===

View File

@@ -8,7 +8,7 @@ endif::[]
Therefore, the User Storage Providers cannot be packaged within any Jakarta EE component or make it an EJB as was the case when Keycloak ran over WildFly in previous versions.
Providers implementations are required to be plain java objects which implement the suitable User Storage SPI interfaces, as was explained in the previous sections. They must be packaged and deployed as stated in the Migration Guide.
Providers implementations are required to be plain java objects which implement the suitable User Storage SPI interfaces, as was explained in the previous sections. They must be packaged and deployed as stated in the Migration Guide.
ifeval::[{project_community}==true]
See https://www.keycloak.org/migration/migrating-to-quarkus#_migrating_custom_providers[Migrating custom providers].
endif::[]
@@ -18,6 +18,6 @@ endif::[]
You can still implement your custom `UserStorageProvider` class, which is able to integrate an external database by JPA Entity Manager, as shown in this example:
- {quickstartRepo_link}/tree/latest/extension/user-storage-jpa
- {quickstartRepo_link}/tree/main/extension/user-storage-jpa
CDI is not supported.

View File

@@ -11,8 +11,8 @@ Connect and SAML protocols.
ifeval::[{project_community}==true]
==== Java
* {quickstartRepo_link}/tree/latest/jakarta/servlet-authz-client[Wildfly Elytron OIDC]
* {quickstartRepo_link}/tree/latest/spring/rest-authz-resource-server[Spring Boot]
* {quickstartRepo_link}/tree/main/jakarta/servlet-authz-client[Wildfly Elytron OIDC]
* {quickstartRepo_link}/tree/main/spring/rest-authz-resource-server[Spring Boot]
endif::[]
==== JavaScript (client-side)