stianst · Apr 30, 2026 · Apr 28, 2026
@@ -1,5 +1,5 @@
-[[_account-service]]
 
+[[_account-service]]
 == Account Console
 
 {project_name} users can manage their accounts through the Account Console. They can configure their profiles, add two-factor authentication, include identity provider accounts, and oversee device activity.

@@ -1,5 +1,5 @@
-[[_admin_permissions]]
 
+[[_admin_permissions]]
 == Managing access to realm resources
 
 Each realm created on the {project_name} has a dedicated Admin Console from which that realm can be managed.

@@ -1,5 +1,5 @@
-[[_fine_grained_permissions]]
 
+[[_fine_grained_permissions]]
 === Delegating realm administration using permissions
 
 You can delegate realm management to other administrators, the realm administrators, using the fine-grained admin permissions

@@ -1,5 +1,5 @@
-[[_master_realm_access_control]]
 
+[[_master_realm_access_control]]
 === Master realm access control
 
 The `master` realm in {project_name} is a special realm and treated differently than other realms.
@@ -11,10 +11,10 @@ It's possible to create multiple superusers,  as well as users that can only man
 ==== Global roles
 
 There are two realm-level roles in the `master` realm.
-These are: 
+These are:
 
 * admin
-* create-realm        
+* create-realm
 
 Users with the `admin` role are superusers and have full access to manage any realm on the server.  Users with the `create-realm` role
 are allowed to create new realms.  They will be granted full access to any new realm they create.
@@ -28,7 +28,7 @@ Each realm in {project_name} is represented by a client in the `master` realm.
 The name of the client is `<realm name>-realm`.  These clients each have client-level roles defined which define varying
 level of access to manage an individual realm.
 
-The roles available are: 
+The roles available are:
 
 * create-client
 * impersonation

@@ -1,5 +1,5 @@
-[[_per_realm_admin_permissions]]
 
+[[_per_realm_admin_permissions]]
 === Dedicated realm admin consoles
 
 Each realm has a dedicated Admin Console that can be accessed by going to the url `{kc_admins_path}/{realm-name}/console`.

@@ -1,3 +1,4 @@
+
 [id="assembly-managing-organizations_{context}"]
 [[_managing_organizations]]
 ==  Managing organizations

@@ -1,3 +1,4 @@
+
 [id="assembly-managing-workflows_{context}"]
 [[_managing_workflows]]
 ==  Managing workflows

@@ -1,3 +1,4 @@
+
 [[_identity_broker_kubernetes]]
 === Kubernetes identity providers
 

@@ -1,5 +1,5 @@
-[[_identity_broker_post_login_flow]]
 
+[[_identity_broker_post_login_flow]]
 === Post login flow
 
 Post login flow is useful for the situations when you want to trigger some additional authentication actions after every login with the particular identity provider.

@@ -1,3 +1,4 @@
+
 [[_oid4vci]]
 == Configuring {project_name} as a Verifiable Credential Issuer
 

@@ -1,3 +1,4 @@
+
 [[_limit-authentication-sessions]]
 === Limit Authentication Sessions
 

@@ -1,3 +1,4 @@
+
 [[read_only_user_attributes]]
 === Read-only user attributes
 

@@ -1,3 +1,4 @@
+
 [[ssrf]]
 === Mitigating Server-Side Request Forgery (SSRF)
 

@@ -1,3 +1,4 @@
+
 [[validate_user_attributes]]
 === Validate user attributes
 
@@ -7,4 +8,4 @@ Administrators should not allow unmanaged attributes for users to prevent attack
 Attributes should have a validation that restricts the amount of data entered by attackers.
 
 When using regular expressions to validate user attributes, avoid regular expressions that use an excessive amount of memory or CPU.
-See https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS[OWASP's Regular expression Denial of Service] for details.
+See https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS[OWASP's Regular expression Denial of Service] for details.
@@ -1,6 +1,5 @@
 
 [[_vault-administration]]
-
 == Using a vault to obtain secrets
 
 {project_name} currently provides two out-of-the-box implementations of the Vault SPI: a plain-text file-based vault and Java KeyStore-based vault.
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,4 @@

		[[_identity_broker_kubernetes]]
		=== Kubernetes identity providers

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,4 @@

		[[_oid4vci]]
		== Configuring {project_name} as a Verifiable Credential Issuer

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,4 @@

		[[_limit-authentication-sessions]]
		=== Limit Authentication Sessions

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,4 @@

		[[read_only_user_attributes]]
		=== Read-only user attributes

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,4 @@

		[[ssrf]]
		=== Mitigating Server-Side Request Forgery (SSRF)

Expand Down