website/docs: update references for new docusaurus version
Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
This commit is contained in:
@ -26,7 +26,7 @@ A Provider is a way for other applications to authenticate against authentik. Co
|
||||
|
||||
At a base level a policy is a yes/no gate. It will either evaluate to True or False depending on the Policy Kind and settings. For example, a "Group Membership Policy" evaluates to True if the user is member of the specified Group and False if not. This can be used to conditionally apply Stages, grant/deny access to various objects, and for other custom logic.
|
||||
|
||||
See [Policies](./policies/index.md)
|
||||
See [Policies](./policies/)
|
||||
|
||||
### Stages & Stages
|
||||
|
||||
@ -34,13 +34,13 @@ Flows are an ordered sequence of stages. These flows can be used to define how a
|
||||
|
||||
A stage represents a single verification or logic step. They are used to authenticate users, enroll users, and more. These stages can optionally be applied to a flow via policies.
|
||||
|
||||
See [Flows](./flow/flows.md)
|
||||
See [Flows](./flow/)
|
||||
|
||||
### Property Mappings
|
||||
|
||||
Property Mappings allow you to make information available for external applications. For example, if you want to login to AWS with authentik, you'd use Property Mappings to set the user's roles in AWS based on their group memberships in authentik.
|
||||
|
||||
See [Property Mappings](./property-mappings/index.md)
|
||||
See [Property Mappings](./property-mappings/)
|
||||
|
||||
### Outpost
|
||||
|
||||
@ -48,4 +48,4 @@ An outpost is a separate component of authentik, which can be deployed anywhere,
|
||||
|
||||
Currently there is only a reverse-proxy outpost, in the future there will be more different outpost types.
|
||||
|
||||
See [Outposts](./outposts/outposts.md)
|
||||
See [Outposts](./outposts/)
|
||||
|
||||
@ -9,7 +9,7 @@ This feature is still in technical preview, so please report any Bugs you run in
|
||||
You can configure an LDAP Provider for applications that don't support any newer protocols or require LDAP.
|
||||
|
||||
:::info
|
||||
Note: This provider requires the deployment of the [LDAP Outpost](../outposts/outposts.md)
|
||||
Note: This provider requires the deployment of the [LDAP Outpost](../outposts/)
|
||||
:::
|
||||
|
||||
All users and groups in authentik's database are searchable. Currently, there is limited support for filters (you can only search for objectClass), but this will be expanded in further releases.
|
||||
@ -76,5 +76,5 @@ This enables you to bind on port 636 using LDAPS, StartTLS is not supported.
|
||||
|
||||
## Integrations
|
||||
|
||||
See the integration guide for [sssd](../../integrations/services/sssd/index) for
|
||||
See the integration guide for [sssd](../../integrations/services/sssd/) for
|
||||
an example guide.
|
||||
|
||||
@ -19,7 +19,7 @@ This update brings a lot of big features, such as:
|
||||
|
||||
This is a new Object type, currently used only by the Proxy Provider. It manages the creation and permissions of service accounts, which are used by the outposts to communicate with authentik.
|
||||
|
||||
See [Outposts](../outposts/outposts.md)
|
||||
See [Outposts](../outposts/)
|
||||
|
||||
- Flow Import/Export
|
||||
|
||||
|
||||
Reference in New Issue
Block a user