add version tag

Author: evelinadanielsson

modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc

@@ -387,8 +387,11 @@ Instead, they are assigned the version given by xref:configuration/configuration
 Alternatively, you can specify the version in the `CREATE ALIAS` or `ALTER ALIAS` commands.
 See xref:database-administration/aliases/manage-aliases-standard-databases.adoc#set-default-language-for-remote-database-aliases[] and xref:database-administration/aliases/manage-aliases-standard-databases.adoc#alter-default-language-remote-database-alias[] for more information.
 
-When creating a remote database alias, the credentials used to target to the remote DBMS need to be specified. This can be done by providing the credentials of a native user, or
-by forwarding the OIDC credentials of the user logged in to the local DBMS.
+When creating a remote database alias, the credentials used to target to the remote DBMS need to be specified and can be either:
+
+* `STORED NATIVE CREDENTIALS`, i.e. the credentials of a single user on the remote DBMS.
+* `OIDC CREDENTIAL FORWARDING`, i.e. passing the bearer authentication token from the user logged in through SSO and who issues the query. Introduced in 2025.10
+by forwarding the OIDC credentials of the user logged in to the local DBMS. label:new[Introduced in 2025.10]
 
 To use the credentials of a native user on the remote DBMS, `USER` and `PASSWORD` need to be set when creating the alias.
 

modules/ROOT/pages/database-administration/aliases/remote-database-alias-configuration.adoc

@@ -23,7 +23,7 @@ A remote alias defines:
 When creating the remote database alias, it can be configured to authenticate with either:
 
 * `STORED NATIVE CREDENTIALS`,  i.e. the credentials of a single user on the remote **DBMS B**.
-* `OIDC CREDENTIAL FORWARDING`, i.e. passing the bearer authentication token from the user who issues the query. In order to use this method to authenticate, the local *DBMS A* and remote *DBMS B* needs to have SSO authentication and authorization through identity providers implementing the OIDC standard configured, see the xref:authentication-authorization/sso-integration.adoc[SSO integration] on how to configure OIDC identity providers.
+* `OIDC CREDENTIAL FORWARDING`, i.e. passing the bearer authentication token from the user logged in through SSO and who issues the query. label:new[Introduced in 2025.10]
 
 
 [[setup-example-stored-native-credentials]]
@@ -200,6 +200,7 @@ If there is a failure when reading the keystore file, investigate the `debug.log
 In case it is not possible to connect to the remote alias after its creation, verify its settings by connecting to the remote database at https://browser.neo4j.io/ or at your local browser.
 ====
 
+[role=label--new-2025.10]
 [[setup-example-credential-forwarding]]
 == Setup example with OIDC credential forwarding