Skip to content

Latest commit

 

History

History
46 lines (31 loc) · 2.43 KB

iam-identify-inactive.md

File metadata and controls

46 lines (31 loc) · 2.43 KB
copyright lastupdated keywords subcollection
years
2022
2022-09-12
inactive identity, inactive identities, inactive, inactive users, inactive service IDs, inactive trusted profiles, inactive API keys
account

{{site.data.keyword.attribute-definition-list}}

Identifying inactive identities

{: #id-inactive-identities}

Identities are considered inactive when they haven't logged in or been in use in 30 days. You can review which users, service IDs, trusted profiles, and API keys in your account are inactive. You might want to remove inactive identities if they are no longer needed. Removing access for inactive identities can reduce the risk of unauthorized access to your IBM Cloud resources and help you manage access more efficiently. To manage inactive identities, you must be assigned the Administrator role on the IAM Identity Service. {: shortdesc}

When you delete an identity from the table, for example a user, and click Update report, it takes a few minutes for a new report to exclude the deleted user. {: note}

Managing inactive identities in the console

{: #manage-inactive-identities}

To view inactive identities in the console, complete the following steps:

  1. In the {{site.data.keyword.cloud_notm}} console, click Manage > Access (IAM), and select Inactive identities.

  2. Click Update report to view the most recent report of the inactive identities in your account.

    Only the most recent report is available. Reports older than a day are deleted when generating a new report. {: note}

  3. Select a tab to review a list of inactive identities.

  4. To delete inactive identities that are no longer in use, click the Actions icon Actions icon > Remove.

Before you delete an identity, confirm that they are inactive for at least 30 days. {: note}

To learn more about the implications of removing or deleting identities in your account, review the following documentation: