trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix build 

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
Jens Langhammer 2024-01-08 14:15:26 +01:00
parent 1a9491fac4
commit 47a0e178d7
No known key found for this signature in database
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/flow/stages/identification/index.md
View File

@ -12,7 +12,7 @@ Select which fields the user can use to identify themselves. Multiple fields can
- Email - Email
- UPN - UPN
UPN will attempt to identify the user based on the `upn` attribute, which can be imported with an [LDAP Source](/integrations/sources/ldap/index) UPN will attempt to identify the user based on the `upn` attribute, which can be imported with an [LDAP Source](/integrations/sources/ldap/)
## Password stage ## Password stage

2
website/docs/user-group-role/groups/manage_groups.md
View File

@ -24,7 +24,7 @@ To edit the group's name, parent group, whether or not the group is for superuse
To [add or remove users](../user/user_basic_operations.md#add-a-user-to-a-group) from the group, or to manage permissions assigned to the group, click on the name of the group to go to the group's detail page. To [add or remove users](../user/user_basic_operations.md#add-a-user-to-a-group) from the group, or to manage permissions assigned to the group, click on the name of the group to go to the group's detail page.
For more information about permissions, refer to ["Assign or remove permissions for a specific group"](../access-control/manage_permissions.md#assign-or-remove-permissions-for-a-specific-group). For more information about permissions, refer to ["Assign or remove permissions for a specific group"](../access-control/manage_permissions.md#assign-or-remove-permissions-on-a-specific-group).
## Delete a group ## Delete a group

4
website/docs/user-group-role/roles/manage_roles.md
View File

@ -15,7 +15,7 @@ To create a new role, follow these steps:
1. In the Admin interface, navigate to **Directory > Roles**. 1. In the Admin interface, navigate to **Directory > Roles**.
2. Click **Create**, enter the name of the role, and then click **Create** in the modal. 2. Click **Create**, enter the name of the role, and then click **Create** in the modal.
3. Next, [assign permissions to the role](../access-control/permissions.md#assign-or-remove-permissions-for-a-specific-role). 3. Next, [assign permissions to the role](../access-control/manage_permissions.md#assign-or-remove-permissions-for-a-specific-role).
## Modify a role ## Modify a role
@ -23,7 +23,7 @@ To modify a role, follow these steps:
- To edit the name of the role, click the Edit icon beside the role's name. - To edit the name of the role, click the Edit icon beside the role's name.
- To modify the permissions that are assigned to the role click on the role's name to go to the role's detail page. There you can add, modify, or remove permissions. For more information, refer to ["Assign or remove permissions for a specific role"](../access-control/permissions.md#assign-or-remove-permissions-for-a-specific-role). - To modify the permissions that are assigned to the role click on the role's name to go to the role's detail page. There you can add, modify, or remove permissions. For more information, refer to ["Assign or remove permissions for a specific role"](../access-control/manage_permissions.md#assign-or-remove-permissions-for-a-specific-role).
## Delete a role ## Delete a role

2
website/integrations/services/organizr/index.md
View File

@ -74,5 +74,5 @@ LDAP Backend Type: `OpenLDAP`
Access for authentik users is managed locally within organizr under _User Management_. By default, new users are assigned the `User` group. Access for authentik users is managed locally within organizr under _User Management_. By default, new users are assigned the `User` group.
::: :::
:::tip :::tip
Consider front-ending your application with a [forward auth provider](../../../docs/providers/proxy/forward_auth#nginx) for an SSO experience. Consider front-ending your application with a [forward auth provider](../../../docs/providers/proxy/forward_auth) for an SSO experience.
::: :::