Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IdentityStore active field #3809

Closed
2 tasks
kevin-manson-dw opened this issue Aug 4, 2023 · 2 comments
Closed
2 tasks

IdentityStore active field #3809

kevin-manson-dw opened this issue Aug 4, 2023 · 2 comments
Assignees
Labels
duplicate This issue is a duplicate. feature-request This issue requests a feature. service-api This issue is caused by the service API, not the SDK implementation.

Comments

@kevin-manson-dw
Copy link

Describe the feature

Enable returning the active field in the IdentityStore.Client.list_users command
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/identitystore/client/list_users.html

The singlesignon docs show this field is available.
https://docs.aws.amazon.com/singlesignon/latest/developerguide/listusers.html

Use Case

As a user we are looking to automate deleting disabled users in AWS AWS IAM Identity Center, currently boto3 does not return the " "active": false," field to determine if a user is active.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

SDK version used

1.28.19

Environment details (OS name and version, etc.)

MacOS

@kevin-manson-dw kevin-manson-dw added feature-request This issue requests a feature. needs-triage This issue or PR still needs to be triaged. labels Aug 4, 2023
@kevin-manson-dw
Copy link
Author

Sorry I was wrong it looks like the core API doesn't have the active field. This is a deeper issue than just boto3

https://docs.aws.amazon.com/singlesignon/latest/IdentityStoreAPIReference/API_ListUsers.html

@tim-finnigan tim-finnigan self-assigned this Aug 4, 2023
@tim-finnigan
Copy link
Contributor

Hi @kevin-manson-dw thanks for reaching out. As you mentioned above this is a limitation in the IdentityStore API. We forwarded this request to the IdentityStore team before (see: aws/aws-sdk#477) and this was the latest update:

Hi all, thanks for your patience and feedback. We heard back from a member of the IdentityStore team and they have acknowledged the feature request but it is not currently on their roadmap. We recommend reaching out through AWS Support if you have a support plan to "+1" the request and help the team gauge demand for this feature...

Please feel free to check back in on that issue for updates in the future, and let us know if you had any other questions.

@tim-finnigan tim-finnigan added duplicate This issue is a duplicate. service-api This issue is caused by the service API, not the SDK implementation. and removed needs-triage This issue or PR still needs to be triaged. labels Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue is a duplicate. feature-request This issue requests a feature. service-api This issue is caused by the service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants