Fork me on GitHub
#aws
<
2022-05-26
>
Benjamin18:05:19

what is a good auth strategy for team internal tools - for analytics stuff, the users are not coders. I'm not sure yet if I want to serve my tool as a website, or run as desktop app. If it is local I know sso is an option (I'm wondering if there is something easier for the user than sso - it can be complicated with broken credentials files or something). I think there is cognito but I am not sure if it is a fit for like other users on the same aws account.

thomas19:05:00

Cognito users are not AWS users... just users of your service.

👍 1
thomas19:05:13

(in case you didn't kow that already)

lukasz20:05:06

Deploying something like https://github.com/oauth2-proxy/oauth2-proxy is prolly the best, given how much bad stuff I see about Cognito

orestis06:05:26

We are using Google workspace so we ended up with Google sign in for internal tools.

Benjamin07:05:44

thanks for the tips