awslabs / awslabs/ssosync

Least Privilege : Google Workspace Directory

Open
#320 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
666
Forks
213
Avg merge
1d 7h
Merged PRs (30d)
4

Description

**Is your feature request related to a problem? Please describe.**
Currently ssosync uses:
- a super admin user account
- impersonation (my_customer)
- credentials file

**Describe the solution you'd like**
Eliminate each of these, using:
- service account (down scope to least privilege and Read Only
- customer_id parameter
- Workload Identity federation - integrated with IAM

but because of the large install base, continue to support the historic authentication schema until v3.

Contributor guide

Open the contributing guide

Research direction

The issue does not name files or tests. Start by tracing the existing authentication schema used by the CLI and AWS Lambda paths, then map how impersonation, credentials files, customer_id, service accounts, and Workload Identity Federation would coexist through v3. Done means least-privilege read-only authentication is supported while the historic schema continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, google-cloud
Domain
authentication, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.