remove role=

neo4j · Dec 23, 2024 · 708c79a · 708c79a
1 parent 2ae6c71
commit 708c79a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/modules/ROOT/pages/authentication-authorization/sso-integration.adoc b/modules/ROOT/pages/authentication-authorization/sso-integration.adoc
@@ -271,7 +271,7 @@ dbms.security.oidc.mysso.get_groups_from_user_info=true
 +
 It is possible to fetch just the username, just the groups, or both from the userinfo endpoint.
 
-[role=]
+
 [[auth-sso-auth-providers]]
 === Configure SSO at the user level using auth providers
 xref:authentication-authorization/auth-providers.adoc[User auth providers] can be used to determine which users can authenticate and authorize using the configured providers.

diff --git a/modules/ROOT/pages/clustering/databases.adoc b/modules/ROOT/pages/clustering/databases.adoc
@@ -259,7 +259,7 @@ neo4j@neo4j> DRYRUN REALLOCATE DATABASES;
 +----------------------------------------------------------------------------------------------------------------------------------------+
 ----
 
-[role=]
+
 [[recreate-databases]]
 == Recreate a database
 
@@ -269,7 +269,7 @@ Neo4j 5.24 introduces the xref:procedures.adoc#procedure_dbms_cluster_recreateDa
 
 * To make your database write-available again after it has been lost (for example, due to a disaster).
 See xref:clustering/disaster-recovery.adoc[Disaster recovery] for more information.
- 
+
 [CAUTION]
 ====
 The recreate procedure works only for real user databases and not for composite databases, or the `system` database.