UMA Integration into Account Management

User Microservice Authentication (UMA) is intergating with Account Management to streamline the authentication and authorization processes for microservices. These changes will be live in Sandbox in May with a tentative Production release in July; exact dates to be announced. More information can be found here. 

Here's is a list of required changes to AMO after UMA intergation:

Different Authentication

1. URL (to be used for all end points): api/auth/login will become uma/api/v1/auth/b2b/login/api-keys

2. api_key and api_secret updated

3. Handle refresh of the JWT using new refresh token

4. TTL is much shorter of access token

Create Applicant 

User creation endpoint has been removed from AccountMangement service and now needs to be accessed in UMA: 

1. Url change: /uma/api/v1/users/b2c

2. Role property before was a string “applicant”. Now it is an array: roles : []

3. branch_id was an integer before and has now an array: branches: []

4. Removed requirement to sent locale_id and password_confirmation fields

Application Creation 

1. As user is created in different service you’ll get a different response body than before

2. Application create request will require you to send uma_user_id field instead of user_id

3. uma_user_id is the “id” property returned by the create endpoint