Adding attributes for section links so they work in upstream and downstream

Closes #43286

Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
This commit is contained in:
Alexander Schwartz 2025-10-08 16:37:13 +02:00 committed by GitHub
parent 6f36a02ffe
commit 94d428d450
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 5 additions and 1 deletions

View File

@ -71,6 +71,8 @@
:developerguide_actiontoken_name: Action Token Handler SPI
:developerguide_actiontoken_link: {developerguide_link}#_action_token_handler_spi
:developerguide_jsproviders_name: JavaScript Providers
:developerguide_userstoragespi_link: {developerguide_link}#_user-storage-spi
:developerguide_userstoragespi_name: User Storage SPI
:developerguide_jsproviders_link: {developerguide_link}#_script_providers
:importexportguide_link: https://www.keycloak.org/nightly/server/importExport
:gettingstarted_name: Getting Started Guide

View File

@ -30,6 +30,8 @@
:quickstartRepo_dir: keycloak-quickstarts
:securing_apps_link: https://www.keycloak.org/guides#securing-apps
:upgrading_guide_link: {project_doc_base_url}/upgrading/
:developerguide_userstoragespi_link: {developerguide_link}#_user-storage-spi
:developerguide_userstoragespi_name: User Storage SPI
:kc_js_path: /js
:kc_realms_path: /realms
:kubernetes: Kubernetes

View File

@ -368,7 +368,7 @@ to be your `wait_timeout` minus a few minutes. Failure to correctly configure th
{project_name} allows you to specify additional datasources in case you need to access another database from your extensions. This is useful when using the main {project_name} datasource is not a viable option for storing custom data, like users.
You can find more details on how to connect to your own users database in the link:{server_developer_guide}#_user-storage-spi[User Storage SPI] documentation.
You can find more details on how to connect to your own users database in the link:{developerguide_userstoragespi_link}[{developerguide_userstoragespi_name}] documentation.
Defining multiple datasources works like defining a single datasource, with one important change - you have to specify a name for each datasource as part of the config option name.