Make lists based on platform users #5

Closed
opened 2024-03-05 06:04:31 +00:00 by ayakael · 3 comments
ayakael commented 2024-03-05 06:04:31 +00:00 (Migrated from lab.ilot.io)

It'd be nice to create lists based on platform use. Not everyone uses every service. Thus, in case of targetted maintenance, we could email just those who have used the respective platform. We can use the GET /core/applications/$slug/used_by/ API object to figure that out. A response looks like this:

[
  {
    "app": "authentik_stages_consent",
    "model_name": "userconsent",
    "pk": "xxx",
    "name": "User Consent $sluf by xxx",
    "action": "CASCADE"
  }
]

We can get all existing slugs via get /core/applications/

It'd be nice to create lists based on platform use. Not everyone uses every service. Thus, in case of targetted maintenance, we could email just those who have used the respective platform. We can use the `GET /core/applications/$slug/used_by/` API object to figure that out. A response looks like this: ``` [ { "app": "authentik_stages_consent", "model_name": "userconsent", "pk": "xxx", "name": "User Consent $sluf by xxx", "action": "CASCADE" } ] ``` We can get all existing slugs via `get /core/applications/`
ayakael commented 2024-03-05 16:27:21 +00:00 (Migrated from lab.ilot.io)

used_by eventually expires. We'll need another approach. It works for Nextcloud as you often relogin, but for Mastodon it is not the best.

`used_by` eventually expires. We'll need another approach. It works for Nextcloud as you often relogin, but for Mastodon it is not the best.
ayakael commented 2024-03-05 16:33:23 +00:00 (Migrated from lab.ilot.io)

GET "https://auth.ilot.io/api/v3/core/user_consent/?user=pk is a good alternative

`GET "https://auth.ilot.io/api/v3/core/user_consent/?user=pk` is a good alternative
ayakael commented 2024-03-05 21:26:08 +00:00 (Migrated from lab.ilot.io)

Implemented, although it only adds people to the respective app group when they've logged in semi-recently. For those logged in permanently it wont keep them in. Closing and opening another issue

Implemented, although it only adds people to the respective app group when they've logged in semi-recently. For those logged in permanently it wont keep them in. Closing and opening another issue
ayakael (Migrated from lab.ilot.io) closed this issue 2024-03-05 21:26:09 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: forge/authentik-listmonk-bridge#5
No description provided.