website/docs: rework user reference page (#6777)
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
parent
5ea67398ae
commit
dda69f2bcc
|
@ -2,6 +2,46 @@
|
||||||
title: User
|
title: User
|
||||||
---
|
---
|
||||||
|
|
||||||
|
## Object properties
|
||||||
|
|
||||||
|
The User object has the following properties:
|
||||||
|
|
||||||
|
- `username`: User's username.
|
||||||
|
- `email` User's email.
|
||||||
|
- `uid` User's unique ID
|
||||||
|
- `name` User's display name.
|
||||||
|
- `is_staff` Boolean field if user is staff.
|
||||||
|
- `is_active` Boolean field if user is active.
|
||||||
|
- `date_joined` Date user joined/was created.
|
||||||
|
- `password_change_date` Date password was last changed.
|
||||||
|
- `path` User's path, see [Path](#path)
|
||||||
|
- `attributes` Dynamic attributes, see [Attributes](#attributes)
|
||||||
|
- `group_attributes()` Merged attributes of all groups the user is member of and the user's own attributes.
|
||||||
|
- `ak_groups` This is a queryset of all the user's groups.
|
||||||
|
|
||||||
|
You can do additional filtering like
|
||||||
|
|
||||||
|
```python
|
||||||
|
user.ak_groups.filter(name__startswith='test')
|
||||||
|
```
|
||||||
|
|
||||||
|
see [here](https://docs.djangoproject.com/en/3.1/ref/models/querysets/#id4)
|
||||||
|
|
||||||
|
To get the name of all groups, you can do
|
||||||
|
|
||||||
|
```python
|
||||||
|
[group.name for group in user.ak_groups.all()]
|
||||||
|
```
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
List all the User's group names:
|
||||||
|
|
||||||
|
```python
|
||||||
|
for group in user.ak_groups.all():
|
||||||
|
yield group.name
|
||||||
|
```
|
||||||
|
|
||||||
## Path
|
## Path
|
||||||
|
|
||||||
:::info
|
:::info
|
||||||
|
@ -53,42 +93,3 @@ additionalHeaders:
|
||||||
```
|
```
|
||||||
|
|
||||||
These headers will now be passed to the application when the user logs in. Most applications will need to be configured to accept these headers. Some examples of applications that can accept additional headers from an authentik Proxy Provider are [Grafana](https://grafana.com/docs/grafana/latest/auth/auth-proxy/) and [Tandoor Recipes](https://docs.tandoor.dev/features/authentication/).
|
These headers will now be passed to the application when the user logs in. Most applications will need to be configured to accept these headers. Some examples of applications that can accept additional headers from an authentik Proxy Provider are [Grafana](https://grafana.com/docs/grafana/latest/auth/auth-proxy/) and [Tandoor Recipes](https://docs.tandoor.dev/features/authentication/).
|
||||||
|
|
||||||
## Object attributes
|
|
||||||
|
|
||||||
The User object has the following attributes:
|
|
||||||
|
|
||||||
- `username`: User's username.
|
|
||||||
- `email` User's email.
|
|
||||||
- `uid` User's unique ID
|
|
||||||
- `name` User's display name.
|
|
||||||
- `is_staff` Boolean field if user is staff.
|
|
||||||
- `is_active` Boolean field if user is active.
|
|
||||||
- `date_joined` Date user joined/was created.
|
|
||||||
- `password_change_date` Date password was last changed.
|
|
||||||
- `attributes` Dynamic attributes, see above
|
|
||||||
- `group_attributes()` Merged attributes of all groups the user is member of and the user's own attributes.
|
|
||||||
- `ak_groups` This is a queryset of all the user's groups.
|
|
||||||
|
|
||||||
You can do additional filtering like
|
|
||||||
|
|
||||||
```python
|
|
||||||
user.ak_groups.filter(name__startswith='test')
|
|
||||||
```
|
|
||||||
|
|
||||||
see [here](https://docs.djangoproject.com/en/3.1/ref/models/querysets/#id4)
|
|
||||||
|
|
||||||
To get the name of all groups, you can do
|
|
||||||
|
|
||||||
```python
|
|
||||||
[group.name for group in user.ak_groups.all()]
|
|
||||||
```
|
|
||||||
|
|
||||||
## Examples
|
|
||||||
|
|
||||||
List all the User's group names:
|
|
||||||
|
|
||||||
```python
|
|
||||||
for group in user.ak_groups.all():
|
|
||||||
yield group.name
|
|
||||||
```
|
|
||||||
|
|
Reference in New Issue