Identity sources for quarterly-access-review (Okta, Google Workspace, AWS IAM)

Open
#56 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, django, google-cloud, python

Research direction

Start by locating the quarterly-access-review implementation and its existing data sources, then read how provider connections and review reports are handled. The issue names Okta, Google Workspace and AWS IAM, but does not identify files or tests, and the proposed integrations span several providers. Done means read-only data is collected with each provider’s narrowest suitable role, reports exclude credentials and tokens, and a seeded Okta case flags a departed user still assigned to an app.

Written by the indexing model from the issue text.

Description

area: connectors idea

Idea

Give quarterly-access-review the user, group and role data it needs from identity providers and cloud accounts.

Problem

Access reviews need to compare who has access against who should. That data lives in Okta, Google Workspace and AWS IAM, none of which are connected today.

Proposed initial scope

  • Read-only connections: Okta (users, groups, app assignments), Google Workspace (users, groups), AWS IAM (users, roles, attached policies, last-used data).
  • Prefer the narrowest built-in read roles each provider offers, and say which one to use when connecting.
  • Reports name accounts and groups but never include credentials or tokens.

Validation

Seed a test Okta org with a departed user still assigned to an app, and confirm the review flags it.

Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 9m
Merged PRs (30d)
322

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.