Hi Team, We are using the Descope Python SDK for user management and have implemented the User Impersonation feature with consent validation enabled. We currently retrieve user information using: •

descope_client.mgmt.user.search_all()

•

descope_client.mgmt.user.load()

We’ve noticed that the returned user entity does not include the consent expiration field. Could you please confirm whether this field is available via the SDK ?

@Prasad Rahatekar The consent expiration field is not explicitly mentioned as part of the user entity returned by the SDK's

load()

or

search_all()

methods. When loading a user, you can retrieve standard attributes like email, phone, display name, roles, tenants, and custom attributes. Doc The consent expiration is configured when gathering user consent through the

Update User / Impersonation Consent

flow action, where you can set the consent expiration in hours. Doc The consent expiration field does not appear in any of the API endpoints. Check https://docs.descope.com/user-impersonation

Ok, I'll raise a Feature Request on descope portal for this.

Sure @Prasad Rahatekar 🙌

https://ideas.descope.works/p/expose-consent-expiration-field-in-descope-python-sdk-user-apis Hey @Rahul Rijhwani, as discussed I have raised above FR. Can you please share approx timeline for this FR to get resolved ?