I am not able to find how to start a new journey (eg: mobile number change journey) once an old journey (eg : login journey) is completed via mobile SDKs.
From sdks only we find way to trigger authentication journeys with apis like
FRUser.login
or
FRSession.authenticate
Can someone please help to understand how we can start another journey like mentioned above.
Thanks,
The Auth-N process relies on targeting an appropriate “journey” or Auth-N tree.
Identity management requirements are typically not completed by targeting an Auth-N journey, as the user is now “authenticated”… but by performing a POST to the User Self Service API endpoint or equivalent.
Cheers
Hi @tamalsamui,
Yes indeed, initiating thru another journey with an existing session completes automatically - The trick to this is to provide the forceAuth flag (set to rue) with the /authenticate call. Once the user has completed the change password journey, it is my understanding that AM will produce a new session.
==> Authenticate with a browser :: PingAM 7.5.0
Another way would be to change the password at the IDM managed endpoint - a smart way, if you also use the SDK’s OAuth2 module, with an identity platform deployment - is to use this access token as bearer token to access IDM - that token giving authorisation for the user to change the password.
Kind regards
Patrick