Replies: 4 comments
-
Recent support messages reminded me of this. |
Beta Was this translation helpful? Give feedback.
-
I am having exactly the same issue with adult contain, and this prevent me to use Oauth2 user creation in Komga. |
Beta Was this translation helpful? Give feedback.
-
Same issue here. Any news on this feature ? Ability to set default permissions for new users ? Or ability to allow only certains libraries ? |
Beta Was this translation helpful? Give feedback.
-
it would be nice if we could map groups and/or claims to Komga-permissions. but even an ability to set default permissions for new users, like suggested by other people, would be a good start. |
Beta Was this translation helpful? Give feedback.
-
Describe your suggested feature
I have set up Google and GitHub OAuth2 for new users to make an account with the env variable KOMGA_OAUTH2_ACCOUNT_CREATION=true so that any account made does not need me to set it up in advance creating a more seamless process for friends/family when visiting the server.
The issue is that new users made this way have access to all content. For various reasons, this is not ideal. (i.e. restricted content, 18+)
It would be great to add options in the UI so that any new account added is subjected to a standard rule set such as blocking access to certain libraries or having share tags set for new users (that can be altered after account creation as is the current way) so libraries with sensitive content cannot be seen initially unless later approved.
Other details
An alternative to this proposed change would be a pend status is applied to a new account added with OAuth2 and a notification (email, txt, discord push) is sent to any admin accounts for approval/denial with the ability to alter their settings prior to their access.
Acknowledgements
Beta Was this translation helpful? Give feedback.
All reactions