Skip to content
Snippets Groups Projects
Commit 4acdb566 authored by Tanner Prestegard's avatar Tanner Prestegard Committed by GraceDB
Browse files

settings: remove unused ADMIN_MANAGED_GROUPS

This is not needed anymore with the changes to the group infrastructure
which add an optional 'ldap_name' to groups whose membership should be
managed by LDAP queries and shib sessions.
parent f35229e7
No related branches found
No related tags found
No related merge requests found
...@@ -149,16 +149,6 @@ SUPEREVENT_MANAGERS_GROUP = 'superevent_managers' ...@@ -149,16 +149,6 @@ SUPEREVENT_MANAGERS_GROUP = 'superevent_managers'
# Analysis group name for non-GW events # Analysis group name for non-GW events
EXTERNAL_ANALYSIS_GROUP = 'External' EXTERNAL_ANALYSIS_GROUP = 'External'
# Groups directly managed by GraceDB admins
ADMIN_MANAGED_GROUPS = [EM_ADVOCATE_GROUP, EXEC_GROUP, PUBLIC_GROUP,
SUPEREVENT_MANAGERS_GROUP, ACCESS_MANAGERS_GROUP, 'raven_users']
# NOTE: soon, only superevent_managers will be fully managed by us. The other
# groups will be managed by the LIGO auth infrastructure for human users. But
# we will still have to still manage robot account membership in these groups:
# access_managers, executives, and em_advocates.
# NOTE: public_users is also managed by us and has only one member
# (guardian.AnonymousUser)
# Tag to apply to log messages to allow EM partners to view # Tag to apply to log messages to allow EM partners to view
EXTERNAL_ACCESS_TAGNAME = 'lvem' EXTERNAL_ACCESS_TAGNAME = 'lvem'
PUBLIC_ACCESS_TAGNAME = 'public' PUBLIC_ACCESS_TAGNAME = 'public'
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment