jit-groups: Group members don't have permission to activate roles

I have gathered several user accounts in a Google Workspace group and want the members of the group to be able to activate roles from a given set using jit-access.

I followed the documentation to add the IAM binding for this group:

gcloud projects add-iam-policy-binding my-project --member group:jit-test@domain.de --role roles/compute.admin --condition "
title=JIT access,expression=has({}.jitAccessContraint)"

But when a member of the group selects “my-project” in jit-access, the following error pops up:

The project doesn’t exist, or you don’t have permission to activate any roles in this project

jit-access is set up correctly in general, as activating roles works if the IAM binding is made for a single user. What am I missing? The docs clearly (?) note that that users as well as groups are supported.

I’m using other GCP features like IAP with groups as well, and never had a problem with it. So why does it seem jit-access can’t look up the members of the group?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15

Most upvoted comments

‘“Accessing the activation request failed: The calling user is not authorized to access this approval request”’

This error doesn’t seem to be related to groups. Instead, it indicates that there was a username mismatch between:

  • the user that was selected as reviewer
  • the user the approver was signed in as

At the bottom of the page, you can see which username you’re signed in with. Is it possible that you were signed in with the wrong user when trying to approve the request?

Experiencing this same issue on a fresh deploy, utilizing the AssetInventory catalog method from the jump.

I did notice some interesting behavior for multi-party approval flows depending on how the role is associated to the user:

If the requesting user is indirectly granted role via group: Requestor receives error:

The project doesn’t exist, or you don’t have permission to activate any roles in this project

If the requesting user is directly granted role via user principal assignment:

  1. Requestor is able to see and select available roles and proceed to approver selection
  2. All users, including users granted role indirectly via group, are visible in approver selection
  3. Notifications can be sent to all approvers, direct and indirect:
    • Approvers granted role via user principal are able to approve, and role is enabled
    • Approvers granted role via membership in group principal receive the following error:
      • The user $USER is not allowed to activate $ROLE using MPA (HTTP 403: error)