Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/documentation/installation/database-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/documentation/user-guide/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading