Deployment and Operations

Release Notes: Customer Deployed Cloudentity Platform 2.8.0

This article is a summary of new features and changes in Cloudentity version 2.8.0.

October 31, 2022

v2.8.0 Highlights

Comply with Brazilian Open Insurance Initiative

Cloudentity platform now fully supports the Brazilian Open Insurance (OPIN) initiative.

  • The Open Finance Brazil type of workspace is configured to provide industry-specific OPIN configuration, for example, OPIN scopes.

  • Added permission mappings and groups validation required by OPIN. It can be used in the consent creation endpoint.

  • Added the following endpoints from the OPIN spec for consent creation and management:

  • Added DCR requirements support coming from the Open Insurance specification. This includes:

    • Requirement of using mTLS for DCR registration

    • Software statement parsing and validation for the model provided by the specification

    • Software role to scope mapping during DCR

  • Extended mTLS aliases in the OAuth wellknown endpoint to include the backchannel authentication endpoint when Client Initiated Backchannel Authentication method is enabled as required by the OPIN specification.

  • Add an option to configure supported acr (Authentication Context Class Reference) values in the authorization server’s OAuth advanced settings. Workspaces now use whatever is configured in the settings instead of an internal hardcoded list.

Utilize Improved Identity Pools

We added a bunch of new improvements to Cloudentity Identity Pools:

  • User credentials now include the expiresAt parameter. Once the password expires, it fails verification, and the user needs to either reset it or change.

    Password expiry can be utilized when migrating users from external identity sources without their passwords defined. Just provide no password and set the expiry date for a date in the past to trigger password change for your users.

  • Added option to set Preferred Authentication Mechanism useful when both password and OTPs are enabled for an IDP. Now, it is possible to pick the default one that shows up on the login screen.

  • Cloudentity Platform admin users can now manage user identifiers and addresses within Cloudentity Identity Pools. Admins can add new identifiers with the email, mobile, UUID types, or even identifiers coming from external sources. Additionally, admins can add new verifiable email or mobile addresses for users and define whether the address is verified or not.

    Adding new identifiers and addresses

  • Refactored Identity APIs to enable developers to extend them more easily.

Cache Requests in Cloudentity Authorizers

In this release, we improved the Cloudentity authorizer’s integration with the Open Policy Agent’s REGO language so that the caching features in the REGO http.send() function are effective. You can now use the following fields in your REGO policies:

  • cache - Cache HTTP response across OPA queries. Default: false.

  • force_cache - Cache HTTP response across OPA queries and override cache directives defined by the server. Default: false.

  • force_cache_duration_seconds - If the force_cache field is set to true, this field specifies the duration in seconds for the freshness of a cached response.

In Cloudentity v2.8.0, the authorizers provide an inter-query cache that persists across policy validations, which enables calls to the http.send() method to access cached responses from previous policy validations. The cache is recreated on each API discovery cycle, so the duration of cached responses is limited by the authorizer’s discovery interval.

The cache size can be configured via the rego_inter_query_cache_size configuration setting for Cloudentity authorizers:

    rego_inter_query_cache_size: 1000000 # maximum size for the Rego inter-query builtin cache

Major Additions and Changes

[ AUT-7438 ] REGO policies that authorize access to APIs via the MicroPerimeter Authorizers can now take advantage of the Open Policy Agent (OPA) inter-query cache.

[ AUT-6982 ] The redirect_uri query parameter is added for custom login and consent pages. As a result, when a login session is timed out, the user is redirected to the client application, instead of the 404 page.

[ AUT-7166 ] Audit logs now include the report on clients' incorrect certificates when registering the clients via the /dcr endpoint within the CDR workplace.

It grounds on the new DCR Create and Reject audit events available for use in webhooks.

[ AUT-7281 ] Added support for the BASE64_NON_URL_ENCODED_DER client certificate format.


BASE64_NON_URL_ENCODED_DER is the base64-encoded format without URL encoding.

[ AUT-7419 ] Critical and high-level vulnerabilities with Alpine Edge are fixed.

[ AUT-7471 ] For the resource owner credentials grant flow, tokens are issued after applying IDP mapping.

[ AUT-7105 ] Added password expiration support. Once a password is expired, its verification fails and the user is required to change their password.

The expiration date can be set with the following options:

The feature grounds on the expiresAt attribute. It can come in handy for cases when users are migrated without passwords—set no password with the expiredAt date in the past. As a result, the user is required to change their password.

Breaking Changes

[ AUT-7185 ] Now, token_endpoint_auth_method is validated for all client applications—not only registered by developers but also created by administrators as well as with DCR.

The validation is based on the server’s token_endpoint-auth_methods.

[ AUT-7264 ] From this version on, the Azure B2C connector accepts custom domains.

[ AUT-7307 ] The open redirection occurrence on logout is eliminated.

[ AUT-7341 ] POST /fdx/consents/introspect returns FDXConsent.

This covers the following changes:

  • The getFDXConsent value is returned with unified response data instead of the GET /consents/{consentID} response.

  • The granted resources and their IDs are returned with the Resources value instead of GrantedResources.

  • The number of consent fields returned by the /introspect endpoint is limited to getFDXConsent.

Please find the /introspect endpoint API reference updated.

Minor Enhancements

[ AUT-6740 ] Added API management for listing FDX consents.

Now you can filter FDX consents by the following parameters:

  • client_id

  • status

  • resource: provide resourceType and the list of ids

Also, the pagination search is available, like for any other specification.

[ AUT-7080 ] ETags explanation added to the Cloudentity API documentation.

[ AUT-7188 ] Refactored Identity Pools APIs: the admin and system endpoints are split. No changes to the endpoints themselves; however, some changes can arise when rendering libraries from Swagger (for example, package changes).

[ AUT-7248 ] Changed the DCR register error codes from 409 (client already exists) to 400 and 422 (validation error). As a result, 400 now complies with the specification.

[ AUT-7274 ] CDR compliance: consent sharing_duration and ADR client statuses are validated before login.

[ AUT-7275 ] Added API management for revoking FDX consents.

Now, consents, with all the related tokens, can be revoked by client_id. For proper revocation, provide the value for the RevocationDetails parameter.

API returns the number of revoked consents.

[ AUT-7299 ] Added the revocation_reason query parameter to the following endpoints:

revocation_reason helps keep track of why an arrangement has been revoked.

The CDR arrangement revocation reason field must not exceed 256 characters in length.

[ AUT-7277 ] The redirect_uri parameter is now validated when redirect_uri isn’t explicitly requested in the /authorize endpoint call since the client features only one Redirect URI.

[ AUT-7463 ] Added validation for calls to the /identity API. Now, when identity_pool_id points to a non-existing pool, the call fails fast and with the same response.

Bug Fixes

[ AUT-7125 ] For FAPI Advanced compliance, a request object check has been added to make sure that the exp claim is no longer than 60 minutes after the nbf claim, as the FAPI specification requires, see - 5.2.2 -> 13.

[ AUT-7273 ] Added a tooltip indicating that a user has multiple identifiers under Identity Pool > Users > Identifiers. Added a UI entry in the Identity Provider’s user view indicating all identifiers of that user registered in Identity Pool.

[ AUT-7339 ] Removed the unnecessary Subscribe to Scopes link for SAML clients in the application topology view.

[ AUT-7400 ] Addressed a number of vulnerabilities found in Cloudentity’s Docker image.

[ AUT-7464 ] Adjusted the DCR flow for the Open Banking Brazil workspace. Now, when the /register endpoint is used, the following rules are enforced:

  • If request_object_signing_alg is supplied and the value is not PS256, an error is returned.

  • If there is no request_object_signing_alg value supplied, an implicit value of PS256 is set.

This validation is enforced for both signed and unsigned DCR registration requests.

[ AUT-7256 ] Fixed a bug where if one user wanted to grant 2 consents, and the scopes of the second consent were granted with the first consent, they were not granted for the second consent at all.

If the list of scopes in the first and second consent was the same, then the second consent was granted with no scopes at all.

Database Version
CockroachDB 22.1.1
Redis 6.2.7
TimescaleDB 2.8.0 (with Postgres 14.5)
Updated: Jan 31, 2023