angadn / auth Goto Github PK

The idea is to move the purely MySQL backed Repository and GroupRepository to AWS-Cognito implementations. The Policy lookups will currently stay as-is, and there is currently no plan to support IAM via this library. However, one may use IAM Roles directly for RBAC policy-verification and this library as a helpful gRPC Middleware.

We need an API that optionally allows another User to be verified as well

When using AWS Cognito, it is the RBAC interface that verifies a User#Secret() for us. Therefore, our main application's User entity needn't always hold a Secret or IsVerified as those are being populated from AWS. Moreover, if auth library itself doesn't use those fields anywhere else.

Proposal
An application can embed a new struct like so:

import (
    ...
    "auth"
    ...
)

...

type AppUser struct {
    auth.RBACUser
}

This would implement the interface methods for AppUser.