Skip to content

Request - Provider Auth Config should not protect based on HTTP Verb #191

@joneubank

Description

@joneubank

Summary of request

This is a proposal for updating the AuthConfig. I am looking for comments and feedback on approach before modifying the existing setup.

The current AuthConfig for the lyric data provider requests a list of HTTP Verbs for enabling auth for data access. In practice, we want all auth enabled by default. Instead of configuring auth by verbs, we should include functional groups of endpoints that we can opt to disable auth for.

The expected case for this is a data repository that allows public read of submitted data but restricts writes.

Details

  1. Remove ProtectedMethods array from auth (and from config options in server implementation).
  2. Ensure auth is always enabled by default
  3. Update the auth config to include the following options
    • allowPublicReadData
    • allowPublicWriteData
    • allowPublicManageCategoriesAndDictionaries

If any of the allow options are enabled, functions that perform the listed action will not perform any auth checks on the incoming requests.

Note

There may be some endpoints that do not have any auth enabled by default, these are unaffected by this issue.

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