Epic Goal

• Implement the Oauth tokens section in the new UI

Why is this important?

• Users need a way to authenticate with the Quay API
• Oauth tokens are an existing standard and need to be available for use and modification in the new UI

Scenarios

1. In an organization, a user is able to create an application and a new oauth token for it
2. Token permissions can be scoped and are reviewable prior to creation
3. Existing applications and tokens are visible in the new UI

Acceptance Criteria

• Tests are updated to account for the new scenarios
• Docs has been notified of this new default behavior and that the old UI will be fully removed at the end of the year in the 3.13 release.

Dependencies (internal and external)

1. TBD

Previous Work (Optional):

1. https://www.sketch.com/s/832153d0-6602-4023-9fb1-953ccf25c8d2/a/OmE41nw

Open questions::

1. TBD

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>