From 0434fe219e8044595061249b5bd535766fbb55d6 Mon Sep 17 00:00:00 2001 From: Karsten Thoms Date: Wed, 18 Nov 2026 21:28:50 +0100 Subject: [PATCH] docs: fix database schema links after schema doc split The database schema documentation was split into multiple pages, so database-schema/database-schema.md no longer exists. Point links to the new index.md and identity.md pages. Co-Authored-By: Claude Opus 5.5 --- docs/documentation/installation/database-schema.md | 2 +- docs/documentation/user-guide/security.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/documentation/installation/database-schema.md b/docs/documentation/installation/database-schema.md index ca5dd8a..e64ac6d 100644 --- a/docs/documentation/installation/database-schema.md +++ b/docs/documentation/installation/database-schema.md @@ -7,7 +7,7 @@ description: "Install and update the Operaton database schema used by the Proces --- ## Install the Database Schema -This document will guide you through the installation and update of the Operaton [database schema](../user-guide/process-engine/database/database-schema/database-schema.md) used by the process engine. +This document will guide you through the installation and update of the Operaton [database schema](../user-guide/process-engine/database/database-schema/index.md) used by the process engine. Regardless of the [architecture of your application setup](../introduction/architecture.md), the process engine always requires this database schema. In a production environment, we recommend setting up this schema yourself and reference the prepared database instance in your application configuration. Consult the installation guide related to your setup to configure the database for a [remote engine](../installation/operaton-bpm-run.md), [shared engine](../installation/full/index.md), or [embedded engine](../installation/spring-boot.md) accordingly. diff --git a/docs/documentation/user-guide/security.md b/docs/documentation/user-guide/security.md index 1df4d30..fd51b56 100644 --- a/docs/documentation/user-guide/security.md +++ b/docs/documentation/user-guide/security.md @@ -100,7 +100,7 @@ Someone could use brute force to produce arbitrary amounts of log statements and To perform authentication, Operaton can use two sources: a database or LDAP. -When using the database, usernames and passwords are stored inside the `ACT_ID_USER` table (see [documentation on database schema](process-engine/database/database-schema/database-schema.md#identity)). To protect the passwords stored in the database, Operaton uses two concepts: +When using the database, usernames and passwords are stored inside the `ACT_ID_USER` table (see [documentation on database schema](process-engine/database/database-schema/identity.md#act_id_user)). To protect the passwords stored in the database, Operaton uses two concepts: * **hashing**: instead of storing the password in plain text, a hash is stored. When authenticating, the same hash is generated from the user's input and compared against the hash in the database. If both hashes are equal the authentication attempt is successful. Operaton allows users to configure and customize the hash function used. Please refer the [documentation section on password hashing](../user-guide/process-engine/password-hashing.md) for details. * **salted hashes** to protect the database against rainbow table attacks, Operaton uses salted hashes. Similar to hashing itself, this function can be configured and extended to a user's needs. Please refer the [documentation section on password hashing](../user-guide/process-engine/password-hashing.md) for details.