> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ulm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Digital Identity Management 2023.06 - Release Note

Release Date: June 29, 2023

## Announcements

The following are Digital Identity Management Announcements:

* Documentation is available at our [Knowledge Center](https://docs.vindicia.com/category/marketoneconnect) and the [Developer site](https://developer.m1amdocs.com/documentation/).
* We are in the process of updating documentation and UIs to reflect current product names for the following:
  * **IdP UI** renamed to **Identity app**
  * **Admin app** renamed to **Admin console**
  * **Care app** renamed to **Care console**

## Connect Features and Enhancements

This section describes the key updates in this release:

### Role-Based-Access-Control (RBAC) for Relying Party Role Mapping

From this release, Digital Identity Management implements a security feature that allows role mapping to relying parties (RPs). This feature prevents users roles from propagating across multiple RPs. The specific RP only receives the roles relevant to it. As a result, both the user and the RP are assigned specific roles to form an aggregate role (permission set). When requesting an access token, the assigned user role is retrieved, and then filtered based on the RP's assigned role. This update increases the security and granularity of role assignments within Digital Identity Management.

### API Resource Protection with Authentication Context Class Reference (ACR) and Authentication Methods Reference (AMR)

From this release, Digital Identity Management enhances the protection of API resources with ACR and AMR implementations as well as the inclusion of the max\_age attribute in resource requests. Connect strengthens the authentication process with ACR and AMR by providing additional context and references to verify the user's identity and authentication.

Digital Identity Management leverages the max-age parameter, sent by the RP in the Authorize request, to verify the current time or age of the user's authentication request. If the user's request exceeds the max\_age attribute value, the user needs to login again. This method provides a more robust level of security and authentication validity.

This increased level of authentication ensures that only trusted and verified users gain access to protected API resources. By incorporating ACR, AMR, and processing current requests only, Digital Identity Management provides an added layer of protection to mitigate the risk of unauthorized access.

### Machine-to-Machine (M2M) Activation APIs

From this release, Digital Identity Management introduces a set of new activation APIs for use with M2M requests:

| M2M API | Description |
| - | - |
| DELETE \{\{connect-platform-url}}/activation/user/\{userId}/password | A machine delete request that clears the user's password |
| PATCH \{\{connect-platform-url}}/activation/user/\{userId}/password | A machine patch request that updates the user's password with a random value |
| PATCH \{\{connect-platform-url}}/activation/user/byid/\{userId} | A machine patch request that update the user's details such as a display name |

## Bug Fixes

There are no bug fixes in this release.

## Known Issues

There are no known issues in this release.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.