Users
Manage user accounts and their credential bundles.
Get the current user
Returns the authenticated user making the request. Allowed for every role. bundlePath is the stored location of the certificate bundle, not a download link; use GET /tap/api/v3/users/{userId}/generateBundleUrl.
Get a user
Returns a user by numeric ID. Allowed for an admin or the user themselves. bundlePath is the stored location of the certificate bundle, not a download link; use GET /tap/api/v3/users/{userId}/generateBundleUrl.
Update a user
Updates a user. Only the fields present in the request body are changed; a field sent as null is treated as omitted. Allowed for an admin or the user themselves; only an admin may change userRole, active, commonName, or awsRoles (a non-admin may send them unchanged). An AWS role id the user does not already have must belong to an existing AWS role. Group memberships are updated when fullName, email, or userRole changes. Changing commonName or fullName does not issue a new certificate; use POST /tap/api/v3/users/{userId}/certificate. Certificate files are stored under a name derived from fullName, so after fullName changes, download links point to a bundle that does not exist and POST /tap/api/v3/users/{userId}/certificate/bundle builds a bundle without the user's certificate until the certificate is rebuilt. bundlePath in the response is the stored location of the certificate bundle, not a download link.
Delete a user
Deletes a user and removes their group memberships, certificate files, and certificate bundle. Files stored under an earlier fullName may not be removed. Requires the admin role.
Get a certificate bundle download link
Returns a presigned URL, valid for 12 hours by default, for downloading the user's certificate bundle. The link is generated without checking that the bundle exists. Allowed for an admin or the user themselves.
Rebuild a user certificate
Issues the user a new certificate with a new key pair and password, and rebuilds the certificate bundle. No email is sent. Requires the admin role.
Rebuild a user certificate bundle
Rebuilds and stores the user's certificate bundle from the user's existing certificate files. The certificate is not reissued. Requires the admin role.
Resend the certificate email
Resends the welcome email for the user's certificate bundle. Requires the admin role and email integration. The email is sent whether or not the sendWelcomeEmail setting is on; it includes a download link valid for 12 hours by default when the showBundleLinks setting is on, and attaches the bundle when the sendWelcomeEmailWithAttachment setting is on.
List users
Returns a summary of each user. The complete user is available from GET /tap/api/v3/users/{userId}. Requires the admin role; a caller with the user role receives an empty list. Users with the super_admin role are included only for a super_admin caller. A single page is returned when pageSize, page, nextToken, or q is not blank, or when active or includeCounts is true; otherwise every user is returned, sorted by fullName. A page is sorted by fullName, ignoring case and surrounding whitespace, then by id.
Create a user
Creates a user, issues the user's certificate, and builds the certificate bundle. Requires the admin role. userRole defaults to user when omitted or null. Each AWS role id in awsRoles must belong to an existing AWS role; the default AWS roles are assigned when awsRoles is omitted or empty. When the sendWelcomeEmail setting is on and email integration is enabled, the user is sent a welcome email; it includes a download link valid for 12 hours by default when the showBundleLinks setting is on, and attaches the bundle when the sendWelcomeEmailWithAttachment setting is on. If the download link cannot be generated, the user is still created but no email is sent, and POST /tap/api/v3/users/{userId}/resend can send it later. bundlePath in the response is the stored location of the certificate bundle, not a download link.
Get the current user (v2)
Deprecated; use GET /tap/api/v3/users/current. Returns the authenticated user making the request. Allowed for every role. Differs from v3 only in awsRoles, which lists AWS role objects instead of AWS role ids. bundlePath is the stored location of the certificate bundle, not a download link; use GET /tap/api/v3/users/{userId}/generateBundleUrl.
Get a user (v2)
Deprecated; use GET /tap/api/v3/users/{userId}. Returns a user by numeric ID. Allowed for an admin or the user themselves. Differs from v3 only in awsRoles, which lists AWS role objects instead of AWS role ids. bundlePath is the stored location of the certificate bundle, not a download link; use GET /tap/api/v3/users/{userId}/generateBundleUrl.
Update a user (v2)
Deprecated; use PUT /tap/api/v3/users/{userId}. Differs from v3 only in awsRoles: the request accepts AWS role objects, of which only id is read, as well as AWS role ids, and the response lists AWS role objects. Updates a user. Only the fields present in the request body are changed; a field sent as null is treated as omitted. Allowed for an admin or the user themselves; only an admin may change userRole, active, commonName, or awsRoles (a non-admin may send them unchanged). An AWS role id the user does not already have must belong to an existing AWS role. Group memberships are updated when fullName, email, or userRole changes. Changing commonName or fullName does not issue a new certificate; use POST /tap/api/v3/users/{userId}/certificate. Certificate files are stored under a name derived from fullName, so after fullName changes, download links point to a bundle that does not exist and POST /tap/api/v3/users/{userId}/certificate/bundle builds a bundle without the user's certificate until the certificate is rebuilt. bundlePath in the response is the stored location of the certificate bundle, not a download link.
List users (v2)
Deprecated; use GET /tap/api/v3/users, which behaves identically. Returns a summary of each user. The complete user is available from GET /tap/api/v3/users/{userId}. Requires the admin role; a caller with the user role receives an empty list. Users with the super_admin role are included only for a super_admin caller. A single page is returned when pageSize, page, nextToken, or q is not blank, or when active or includeCounts is true; otherwise every user is returned, sorted by fullName. A page is sorted by fullName, ignoring case and surrounding whitespace, then by id.