Merge branch '11157-builtin-users-oidc-auth' of github.com:IQSS/dataverse into 11157-builtin-users-oidc-auth

Author: GPortas

doc/release-notes/11197-builtin-users-oidc-auth.md

@@ -1,19 +1,21 @@
 ### API_BEARER_AUTH_USE_BUILTIN_USER_ON_ID_MATCH feature flag
 
-Introduced a new feature flag, ``API_BEARER_AUTH_USE_BUILTIN_USER_ON_ID_MATCH``, which allows the use of a built-in user
+A new feature flag called `API_BEARER_AUTH_USE_BUILTIN_USER_ON_ID_MATCH` has been introduced, which allows the use of a built-in user
 account when an identity match is found during OIDC API bearer token authentication.
 
 This feature enables automatic association of an incoming IdP identity with an existing built-in user account, bypassing
 the need for additional user registration steps.
 
+See [the guides](https://dataverse-guide--11193.org.readthedocs.build/en/11193/installation/config.html#feature-flags), #11193, #11197, and #11314.
+
 ### Keycloak SPI for Built-In users
 
-A Keycloak SPI, ``builtin-users-spi``, has been implemented that allows the use of Keycloak on instances with built-in
+A Keycloak SPI, `builtin-users-spi`, has been implemented that allows the use of Keycloak on instances with built-in
 accounts for OIDC
 authentication, enabling the use of the SPA on those instances.
 
 Looking ahead, this authenticator SPI could also support mapping Shibboleth users coming in through Keycloak to existing
 Shib users without changing the provider in the Dataverse database. However, this would require changes to the storage
 provider to support more than just built-in users.
 
-The SPI code is available in the Dataverse code repository.
+The SPI code is available in the Dataverse code repository (`conf/keycloak/builtin-users-spi`).

docker-compose-dev.yml

@@ -59,7 +59,7 @@ services:
         -Ddataverse.pid.fake.label=FakeDOIProvider
         -Ddataverse.pid.fake.authority=10.5072
         -Ddataverse.pid.fake.shoulder=FK2/
-      #-Ddataverse.lang.directory=/dv/lang
+        #-Ddataverse.lang.directory=/dv/lang
     ports:
       - "8080:8080" # HTTP (Dataverse Application)
       - "4949:4848" # HTTPS (Payara Admin Console)