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 August with a later Prod release in September; 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
-
URL (to be used for all end points):
api/auth/login
will becomeuma/api/v1/auth/b2b/login/api-keys
-
api_key
andapi_secret
updated -
Handle refresh of the
JWT
using new refresh token -
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:
-
Url change:
/uma/api/v1/users/b2c
-
Role property before was a string
“applicant”
. Now it is an array:roles : []
-
branch_id
was an integer before and has now an array:branches: []
-
Removed requirement to sent
locale_id
andpassword_confirmation
fields
Application Creation
-
As user is created in different service you’ll get a different response body than before
-
Application create request will require you to send
uma_user_id
field instead ofuser_id
-
uma_user_id
is the“id”
property returned by the create endpoint