Descope

Enhancements
* **Audience claim configuration in verification process**: We now allow passing the audience claim explicitly when verifying the session token. The new `audience` parameter in the `exchange_token` function can receive any string value, or stay empty by default.

Breaking changes
* **Scalable user searching**: We’ve made some improvements to enhance the scalability of our system to better support increased usage. These changes allow us to handle increased demand more efficiently, ensuring a smoother experience for all our customers.
As part of this update, there may be a delay (up to 100ms) in accessing newly written or updated user data from the search user endpoints. If you have any questions, feel free to reach out!

Enhancements
* **User tenant API**: We added an option to fetch a specific user's tenant(s) information from an active session. Using the new `my_tenants` function, you can query a current user's sessions' tenants details. See the example in the SDK's [README](https://github.com/descope/python-sdk?tab=readme-ov-file#my-tenants).
* **Tenant created time**: We added the tenant's creation time when loading the tenant (both in `load` and `load_all` functions).

Enhancements
* **Project tags**: Projects now have a `tags` attribute - a list of strings that can be used to distinguish your projects. Those can be updated using the `update_tags` command.

Bug fixes
* **JWT rotation enablement**: We fixed a bug that we found that caused the JWT rotation feature not to work with this specific SDK. This gap was fixed and now the feature is working properly.

Enhancements
* **Access key descriptions and permitted IPs list**: Access key descriptions can now be set - both from the console as well as the SDK. This also applies for permitted IPs (the source IP that is used by the access key upon request) - which supports both single IP addresses as well as CIDRs.
* **Application sign-out URL**: We've added an option to configure a specific application sign-out URL using the `logout_redirect_url` param in SAML related functions. This is useful when Descope is your IdP, and you want to sign a user out of Descope when they sign out from their SP.
* **User interaction override**: With the `force_authentication` flag in applications, you can force end user to interact in a specific way with Descope (as IdP), regardless of the SP's settings.

Bug fixes
* **Audit timestamps weren't datetimes**: the `from` and `to` audit parameters were fixed to be returned as proper datetime (timestamp) objects.

Enhancements
* **Custom audit events**: We've added the function `create_event` to our `audit` object, that allows you to generate your own custom audit events. You can also create your custom audit event to provide different data than that provided by Descope.
* **Option to automatically delete related users/access keys when deleting their associated tenant**: We've added an option to handle auto-deletion of 'orphaned' users and access keys when their last tenant is deleted. When deleting a tenant, you can use the new `cascade` flag to indicate that if part of the tenant's users/access keys are left with no tenant association - they will also be deleted from the project.
* **ReBAC relationship checker**: We added a new function `what_can_target_access_with_relation` to check what resources a user has access, per the application's ReBAC schema. Search is recursive.
* **TOTP seed migration**: When batch importing users into Descope, you can specify collecting their TOTP seed as part of the migration. If provided in the data, that seed will now be associated with the user and the next authentication will be seamless.
* **Force refresh of OAuth/OIDC provider token**: Current refresh of provider token is based on its expiration time. There are some cases in which the provider doesn't return the expiration, and for that we aded the `forceRefresh` parameter when using the `user_get_provider_token` function - to force refreshing the provider token.

Enhancements
* **OTP via voice**: In addition to sending OTP via SMS or email - we now support a third delivery method - voice call, with the `DeliveryMethod.VOICE` option.