You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/internals/users.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Fractal Server's user model and authentication/authorization systems are powered
5
5
## User Model
6
6
<aname="user-model"></a>
7
7
8
-
A Fractal user corresponds to an instance of the [`UserOAuth`](..//reference/fractal_server/app/models/security.md/#fractal_server.app.models.security.UserOAuth) class, with the following attributes:
8
+
A Fractal user corresponds to an instance of the [`UserOAuth`](../reference/fractal_server/app/models/security.md#fractal_server.app.models.security.UserOAuth) class, with the following attributes:
9
9
10
10
| Attribute | Type | Nullable | Default |
11
11
| :--- | :---: | :---: | :---: |
@@ -15,13 +15,11 @@ A Fractal user corresponds to an instance of the [`UserOAuth`](..//reference/fra
The colored attributes are specific for Fractal users, while the other attributes are [provided](https://github.com/fastapi-users/fastapi-users-db-sqlmodel/blob/main/fastapi_users_db_sqlmodel/__init__.py) by FastAPI Users.
20
+
The colored attribute (`username`) is specific for Fractal users, while the other attributes are [the default ones from `fastapi-users`](https://fastapi-users.github.io/fastapi-users/latest/configuration/schemas/).
23
21
24
-
In the startup phase, `fractal-server`always creates a default user, who also has the superuser privileges that are necessary for managing other users.
22
+
In the startup phase, `fractal-server` creates a default user, who also has the superuser privileges that are necessary for managing other users.
25
23
The credentials for this user are defined via the environment variables
The most common use cases for `fractal-server` are:
35
33
36
34
1. The server is used by a single user (e.g. on their own machine, with the [local backend](runners/local.md)); in this case you may simply customize and use the default user.
37
-
2. The server has multiple users; in this case the admin may use the default user (or another user with superuser privileges) to create additional users (with no superuser privileges). For `fractal-server` to execute jobs on a SLURM cluster (through the corresponding [SLURM backend](runners/slurm.md)), each Fractal must be associated to a cluster user via the `slurm_user` attribute (see [here](runners/slurm.md/#user-impersonation) for more details about SLURM users).
35
+
2. The server has multiple users, and it is connected to a SLURM cluster. For `fractal-server` to execute jobs on the SLURM cluster each Fractal must be associated to a cluster user via additional properties defined in the [`UserSettings` table](../reference/fractal_server/app/models/user_settings.md). See [here](runners/slurm.md/#user-impersonation) for more details about SLURM users.
38
36
39
37
More details about user management are provided in the [User Management section](#user-management) below.
0 commit comments