Summary:
New endpoints added to manage “Partners”
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Can now manage Partners in the User service
...
Summary:
Ability to temporarily disable Create / Update / Delete operations per application
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Previously temporarily disabling CUD operations was only possible for all applications. This has been updated so it is now possible to disable this per application.
...
Summary:
Support for “User Identity”
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Users service now provides an API to:
Get User information by id.
Get User list by OData query with filter by partner
CRUD operations on User Identity
List User identities by UserId.
...
Summary:
User Roles - Restrict access to application functions with the Role-based approach
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Ability to restrict access to application functions with the Role-based approach.
...
Summary:
Removed migration endpoints from Public API
...
GET
/Users/{userName}/migration/status
...
Summary:
OData parameters display as Query parameters
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
GET /users/identities“ or “GET /users“ endpoint
OData parameters now display as Query parameters.
...
Summary:
Correctly returns 404 response when user role not found
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
GET /users/roles/{userRoleId}
Now returns 404 Not Found when user role does not exist.
...
Summary:
Removed extra set of Custom Policies defined for Azure B2C
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Azure B2C had two sets of custom policies defined. This has been changed to one set.
...