Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Summary:
New endpoints added to manage “Partners”

Ticket:
SSO-227 - Getting issue details... STATUS

Detail:
Can now manage Partners in the User service


Summary:
Ability to temporarily disable Create / Update / Delete operations per application

Ticket:
SSO-188 - Getting issue details... STATUS

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:
SSO-190 - Getting issue details... STATUS

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:
SSO-194 - Getting issue details... STATUS

Detail:
Ability to restrict access to application functions with the Role-based approach.


Summary:
Removed migration endpoints from Public API

Ticket:
SSO-216 - Getting issue details... STATUS

Detail:
Removed the following migration end points on Users.App.PublicApi as these are no longer used: 

GET
/Users/migration/status

GET
/Users/{userName}/migration/status


Summary:
OData parameters display as Query parameters

Ticket:
SSO-219 - Getting issue details... STATUS

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:
SSO-224 - Getting issue details... STATUS

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:
SSO-203 - Getting issue details... STATUS

Detail:
Azure B2C had two sets of custom policies defined. This has been changed to one set.




  • No labels