ForgotPassword
ForgotPassword (Start)
Introduction
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and the Subscribe Registration API to create the STARTFORGOTPASSWORD (PWDREQ) event and send an email with a link to the subscriber.
Comparison
Note:
The old model is in PascalCase, while the new model is in CamelCase.
UsersOrchestrator API doesn’t return PasswordResetLinkSent.
URL
/ForgotPassword
/v4/Users/ForgotPassword
Method
POST
POST
Request
Response
ForgotPassword (Start)
POST
/v4/Users/ForgotPassword
This endpoint is used to create the STARTFORGOTPASSWORD (PWDREQ) event and send an email with a link to the subscriber.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Headers
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Request Body
ReturnUrl
String
URL to which users must be redirected after they have successfully verified their registration.
LoginName*
String
Subscriber’s login name.
Events
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
PWDREQ (64)
SUBSCRIBE_USER_STARTFORGOTPASSWORD (4009)
The new event is used to Start forgot password in Subscribe
ForgotPassword (Validate)
Introduction
This endpoint handles the workflow orchestration between the integration services (such as Auth0, Gigya, SSOR, and Firefly) and the Subscribe Registration API to validate whether the received EncryptedEventId is a valid event for the forgot password flow.
Comparison
Note:
The old model is in PascalCase, while the new model is in CamelCase.
The UsersOrchestrator API returns the EventId associated with the user.
If the event is invalid, the UsersOrchestrator API returns an error.
URL
/ForgotPassword/Validity
/v4/Users/ForgotPassword/{{EncryptedEventId}}/Validity
Method
POST
GET
Request
Response
Forgot Password (Validate)
GET
/v4/Users/ForgotPassword/{{EncryptedEventId}}/Validity
This endpoint is used to validate whether the received EncryptedEventId is a valid event for the forgot password flow.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Path Parameters
EncryptedEventId*
String
Encrypted unique identifier of the event.
Headers
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
ForgotPassword (FINISH)
Introduction
This endpoint receives the new password to set based on an event and triggers the UpdatePassword workflow.
Comparison
Note:
The old model is in PascalCase, while the new model is in CamelCase.
If the flow fails, the UsersOrchestrator API returns an error.
URL
/ForgotPassword/ChangePassword
/v4/Users/ForgotPassword/{{EncryptedEventId}}
Method
POST
POST
Request
Response
ForgotPassword (Finish)
POST
/v4/Users/ForgotPassword/{{EncryptedEventId}}
This endpoint receives the new password to set based on an event and triggers the UpdatePassword workflow.
Note: The parameters marked with an asterisk (*) are mandatory and must be included in the input model.
Path Parameters
EncryptedEventId*
String
Encrypted unique identifier of the event.
Headers
Authorization*
String
JSON Web Token used for security purposes
X-SourceSystem*
String
To identify the consumer or the Source System
X-ClientCode*
String
Client Code of the Tenant
X-PaperCode*
String
Paper Code of the Tenant
X-ClientGroupCode*
String
Client Group Code of the Tenant
Request Body
Password*
String
Subscriber’s password.
Events
Note:– The associated Event IDs for the Event Type Codes are specified in parentheses (i.e., EventTypeCode (EventID)) in the table below.
CHGPWD (22)
AUTHSYSTEM_USER_CHANGEPASSWORD (4609)
SUBSCRIBE_USER_CHANGEPASSWORD (4010)
For each CHGPWD old event, we now create two events: one for the call to the third-party system and one for the call to our database.
Last updated