Add `Enabled` property to `CognitoUser`

[ScottShingler]

Describe the feature

The CognitoUser class does not expose information about whether the user account is enabled or disabled. This is an important piece of information that should be exposed, ideally by adding an Enabled property.

Use Case

I am trying to update our ASP.NET Core Identity implementation to use Cognito. This has proved to be frustrating, in part due to the fact that FindByIdAsync doesn't give me information about whether the user account is enabled.

CognitoUserPool.FindByIdAsync calls IAmazonCognitoIdentityProvider.AdminGetUserAsync, which returns an instance of AdminGetUserResponse. AdminGetUserResponse includes the Enabled property. However, the Enabled value is not captured in the instance of CognitoUser that is constructed by FindByIdAsync. Consequently, FindByIdAsync is useless to me, so I have to directly use AdminGetUserAsync to get the information I need instead.

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

AWS .NET SDK and/or Package version used

Amazon.Extensions.CognitoAuthentication 2.5.5

Targeted .NET Platform

.NET 8

Operating System and version

Windows 11

[ashishdhingra]

@ScottShingler Good afternoon. Thanks for opening the issue. Cognito User Pool: AdminGetUser does return Enabled property. However, it is is not captured in the returned CognitoUser object here. There is a Status field in CognitoUser class, but that corresponds to UserStatus field returned in response object as a result of Cognito User Pool: AdminGetUser call.

This needs review with the team.

Thanks,
Ashish

[ScottShingler]

@ashishdhingra Thanks for the quick response! Just want to clarify a couple of things to ensure there are no misunderstandings:

1. The Status field conveys different information than the Enabled property, and therefore cannot be used to infer whether a user account is enabled or not.
2. As a developer, it would be preferable to be able to use the FindByIdAsync method rather than directly calling AdminGetUser since it helps to decouple the identity logic from the AWS SDK.