Skip to content

Missing config collections causing permission edge case #2002

Description

@SHession

Problem

As noted in #2000.

If the config for collections is unavailable the Fronts tool is unable to determine which permissions are required to interact with it. Currently the tool assumes no permissions are required. In practice this should be unlikely but is a potentially dangerous assumption to make.

logger.warn(
"No config found when checking required permissions for a collection"
)
Set.empty[
PermissionsPriority
] // if there are no fronts in config, there can be no permissions....?

We can check the warning logs to see how frequently this case occurs.

Solution

Determine as sensible approach for handling a lack of config when determining required permissions for a collection:

  • Should we assume all permissions are required?
  • Should we simply reject the request with a 5XX error?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions