Class AuthorityConstants

java.lang.Object
ubic.gemma.core.security.AuthorityConstants
public class AuthorityConstants extends Object
Defines constants used in GrantedAuthories. An authority is basically a marker of a level of access; in Gemma this corresponds to the authority on a 'group' of users (UserGroup). There are currently three special groups: Administrators, Users, and Agents. Anonymous is another

Some of these values are originally set by init-entities.sql

Version:
$Id: AuthorityConstants.java,v 1.6 2013/08/21 23:22:22 paul Exp $
Author:
klc, paul
See Also:
  • GrantedAuthority

  • Field Details

    • ROLE_PREFIX

      public static final String ROLE_PREFIX
      Prefix used for roles.

      Spring uses ROLE_ by default.

      See Also:

    • ADMIN_GROUP_AUTHORITY

      public static final String ADMIN_GROUP_AUTHORITY
      The name of the administrator group authority. All administrators must be in this group.
      See Also:

    • ADMIN_GROUP_NAME

      public static final String ADMIN_GROUP_NAME
      The name of the administrator group. Not the same as the group authority!
      See Also:

    • USER_GROUP_AUTHORITY

      public static final String USER_GROUP_AUTHORITY
      The name of the default user group authority. All authenticated users should be in this group or in the administrator group.
      See Also:

    • USER_GROUP_NAME

      public static final String USER_GROUP_NAME
      See Also:

    • RUN_AS_ADMIN_AUTHORITY

      public static final String RUN_AS_ADMIN_AUTHORITY
      Used when we are running at elevated permissions.
      See Also:

    • RUN_AS_USER_AUTHORITY

      public static final String RUN_AS_USER_AUTHORITY
      Used when we are running at elevated permissions.
      See Also:

    • CURATOR_GROUP_AUTHORITY

      public static final String CURATOR_GROUP_AUTHORITY
      Curators do everything an administrator does to DATA — edit designs, change a dataset's visibility, run analyses — and nothing an administrator does to the SERVER or to USER ACCOUNTS. Those two exclusions are enforced at the REST layer, where the routes that manage caches, indices, ontologies, sessions, pipeline batches and user accounts keep hasAuthority('GROUP_ADMIN'); everything else was widened to hasAuthority('GROUP_CURATOR'), which an administrator satisfies through the role hierarchy (Paul, 2026-09-05: "really nothing other than user admin, and I guess server ops").
      See Also:

    • CURATOR_GROUP_NAME

      public static final String CURATOR_GROUP_NAME
      See Also:

    • AGENT_GROUP_AUTHORITY

      public static final String AGENT_GROUP_AUTHORITY
      See Also:

    • AGENT_GROUP_NAME

      public static final String AGENT_GROUP_NAME
      See Also:

  • Constructor Details

    • AuthorityConstants

      public AuthorityConstants()