Table of Contents
This minor update introduces changes for Authlete 3.0. This new version was made available on December 11th (Thu).
Cache-Control: no-store and Pragma: "no-cache" in responses, in accordance to RFC6749cluster and standalone caching backends which adds improvements such as adding retries, selective stale cache key deletion and not relying on flush along with using the latest jedis APIAdded a new admin-only endpoint to retrieve orphaned service IDs.
client_id and publish their metadata at that locationcimdOptions, to the /auth/authorization, /auth/token, /backchannel/authentication and /device/authorization endpointsService property, httpAliasProhibited, which prohibits client ID aliases that start with https:// or http://, in order to prevent possible conflicts between client ID aliases and client IDs in OpenID Federation 1.0 and CIMDcimdMetadataPolicyEnabled and cimdMetadataPolicy propertiesdeleteClientOnUpdateFailure method in the CimdUtils class now removes dependencies from other tables as wellcredential_request_encryption (cf. OID4VCI 1.0 Section 10), which enables credential requests to be encryptedcredential_response_encryption, removing the alg property in favor of including it in the JWK specified by the jwk parameterc_nonce in order to issue it from a dedicated endpointservice table with columns matching the Credential Issuer Metadata parameters defined in the specificationoid4vciVersion property to Service so that Authlete can support multiple versions of the OID4VCI specificationFixed an issue where an old service access token would remain valid after token rotation.
Fixed an issue where the redis-cluster backend would be incorrectly flushed, and improved logging to detect read or write failures to the cache.
Fixed an issue where the Nimbus JOSE+JWT library’s JWSVerificationKeySelector didn’t properly handle EdDSA/OKP keys, causing PRIVATE_KEY_JWT client authentication and DPoP token validation to fail when using EdDSA signatures.
N/A