Fix anchors in the documentation

Closes #43084

Signed-off-by: Martin Bartoš <mabartos@redhat.com>
Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
Co-authored-by: Václav Muzikář <vaclav@muzikari.cz>
Co-authored-by: Alexander Schwartz <alexander.schwartz@ibm.com>

docs/documentation/release_notes/topics/26_4_0.adoc

@@ -177,7 +177,7 @@ To support basic TLS termination (edge) deployments by the operator, you may now
 Some {project_name} use cases like User Federation might require connecting to additional databases.
 This was possible only through specifying unsupported raw Quarkus properties in previous {project_name} versions. In this release, there are now dedicated server options for additional datasources. This allows users to leverage additional databases in their extensions in a supported and user-friendly way.
 
-Read more about it in the link:https://www.keycloak.org/server/db#configure-multiple-datasources[Configure multiple datasources] guide.
+Read more about it in the link:https://www.keycloak.org/server/db#multiple-datasources[Configure multiple datasources] guide.
 
 = Observability
 
@@ -194,7 +194,7 @@ this by setting `spec.serviceMonitor.enabled: false`. For more details, see the
 {project_name} supports HTTP access logging to record details of incoming HTTP requests.
 While access logs are often used for debugging and traffic analysis, they are also important for security auditing and compliance monitoring.
 
-For more information, see https://www.keycloak.org/server/logging[Configuring logging].
+For more information, see https://www.keycloak.org/server/logging#http-access-logging[Configuring logging].
 
 == Showing context information in log messages (preview)
 
@@ -204,5 +204,5 @@ ifeval::[{project_community}==true]
 Thank you to https://github.com/eicki[Björn Eickvonder] for contributing this.
 endif::[]
 
-For more details on this opt-in feature, see https://www.keycloak.org/server/logging[Configuring logging].
+For more details on this opt-in feature, see https://www.keycloak.org/server/logging#mdc[Configuring logging].
 

docs/documentation/server_development/topics/user-storage.adoc

@@ -27,4 +27,4 @@ There are two sample projects in link:{quickstartRepo_link}[{quickstartRepo_name
 
 |===
 
-In order to connect to the external database, you should use the {project_name} properties for the additional datasources described in the link:https://www.keycloak.org/server/db#configure-multiple-datasources[Configure multiple datasources] guide.
+In order to connect to the external database, you should use the {project_name} properties for the additional datasources described in the link:https://www.keycloak.org/server/db#multiple-datasources[Configure multiple datasources] guide.

docs/documentation/tests/src/test/resources/ignored-links

@@ -40,7 +40,8 @@ https://www.npmjs.com/package/*
 # Failing because of broken certificate, can likely be restored later.
 https://docs.kantarainitiative.org*
 https://saml.xml.org*
-# BEGIN - To be removed once KC 26.4 has been released
-https://www.keycloak.org/securing-apps/specifications
-https://www.keycloak.org/server/db#configure-multiple-datasources
-# END
+
+# To be removed once KC 26.4.2 is released
+https://www.keycloak.org/server/db#multiple-datasources
+https://www.keycloak.org/server/logging#http-access-logging
+https://www.keycloak.org/server/logging#mdc

docs/documentation/upgrading/topics/changes/changes-26_4_0.adoc

@@ -43,7 +43,7 @@ db-url-full-user-store=jdbc:postgresql://my-remote-postgres:5432/user-store
 # transactions XA is enabled by default for datasources
 ----
 
-For more information about the datasource options, check the link:https://www.keycloak.org/server/db#configure-multiple-datasources[Configure multiple datasources] guide.
+For more information about the datasource options, check the link:https://www.keycloak.org/server/db#multiple-datasources[Configure multiple datasources] guide.
 
 ==== 2. Remove quoting in `quarkus.properties` (unsupported)
 If you are not able to migrate to the {project_name} datasource options right now, remove the additional datasource name quoting to avoid a clash of the datasource options mapping to prevent any issue.

docs/guides/server/db.adoc

@@ -405,6 +405,7 @@ If you are explicitly configuring the `wait_timeout` in your database, it is nec
 to be your `wait_timeout` minus a few minutes. Failure to correctly configure the `db-pool-max-lifetime` will result in
 {project_name} logging a warning on startup.
 
+[[multiple-datasources]]
 == Configure multiple datasources
 
 {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.

docs/guides/server/logging.adoc

@@ -3,6 +3,7 @@
 <#import "/templates/links.adoc" as links>
 <#import "/templates/profile.adoc" as profile>
 <#import "/templates/options.adoc" as opts>
+<#import "/templates/features.adoc" as features>
 
 <@tmpl.guide
 title="Configuring logging"
@@ -154,17 +155,10 @@ The root level must be set to the most verbose required level (`debug` in this c
 
 In order to see the `org.keycloak.events:trace`, the `trace` level must be set for the Syslog handler.
 
+[[mdc]]
 == Adding context for log messages
 
-:tech_feature_name: Log messages with Mapped Diagnostic Context (MDC)
-:tech_feature_id: log-mdc
-
-[NOTE]
-====
-{tech_feature_name} is
-*Preview*
-and is not fully supported. This feature is disabled by default.
-====
+<@features.techpreview feature="log-mdc"/>
 
 You can enable additional context information for each log line like the current realm and client that is executing the request.
 
@@ -262,6 +256,7 @@ You can change the queue length as follows:
 
 These properties are available only when asynchronous logging is enabled for these specific log handlers.
 
+[[http-access-logging]]
 == HTTP Access Logging
 
 {project_name} supports HTTP access logging to record details of incoming HTTP requests.