| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Ensure new users belong to an Agent
Users may come without the correct group information, leading
to a situation where they have no Agent assigned to them.
The application cannot handle this, so we ensure new users
are at least associated to the new Anonymous Agent.
2. Introduce a default avatar
Users coming without an avatar would see a broken view.
Now they're assigned a default avatar, which shows the IN COMMON
icon logo instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since we moved away from Roles it's important to maintain a
default Agent that is distinct from the previous default
IN COMMON Agent.
Previously, a user without a proper group would be granted the
`observer` role in the default Agent, enough to create new
resources.
Now, we consider anonymous users to be part of the Anonymous
Agent, which also brings the possibility for them to edit yet
to be accepted Resources.
|
| |\ |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
When using SSO, the Discourse sends a list of the user groups.
We take the opportunity to update Agency information for the user.
This is performed as a background job, as it involves networked
requests to the Discourse, e.g., to verify group ownership...
|
| |
|
