Refactor ApiUserService
to separate authentication vs authorization related methods
#8049
Labels
Milestone
Background
This was created from a discussion on #8030's PR review.
ApiUserService
is getting unwieldy. We should refactor this class so that authentication and authorization concerns are separated out.Change requested
Refactor the
ApiUserService
class so that any methods related to authentication (resetting emails, passwords, etc...) are separate from authorization flows (getting orgRoles etc, which have been introduced thanks to the Okta migration work).Acceptance criteria
Dependencies
Open questions
Notes
Additional context
The text was updated successfully, but these errors were encountered: