Non self serving user management in hasura-auth about nhost

[beepsoft]

Besides registering users it would also be great to have the ability to manage sign in of users eg. to have an admin exposed sign in API where the default login related settings can be overridden for each sign in request.

For example:

• Setting token expiration length when signing in a user. The use case for this is that token expiration could be different for users with different roles and we could set a different expiration length on a per user basis.
• Setting requirement for MFA. Again, for some users we want to make it optional, or required. It could again be set wether MFA is required or not at login time.

[plmercereau]

Hello @beepsoft,
Better late than never.

From what I see, it is possible to perform some tasks from the GraphQL endpoint when setting a specific set of permissions to a super user role (or when using the hasura secret except):

• trigger emails
• set password
• authenticate (but I don't think this one should be considered)

About the two examples, it would imply adding new columns in the user table (something like access_token_expires_in and mfa_required). Then, in using the above suggestion, it would be already possible to change these values.

I feel the two examples are bit of an edge case, but feel free to open an issue about each, maybe it will ring a bell to other community members!

[mrkpatchaa]

@plmercereau I was actually looking for how to set longer user sessions without having to refresh.
We're adding offline capability to our application and we would like people to login in the morning, disconnect from internet and then synchronize their work at the end of the day for example.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.