On my v66 machines, the API call in question (created with create_user_session) delivers users to their hosting accounts. But the same call on v68 is delivering users to an invalid version of
Password & Security
Change Password
page
It is invalid in the sense that, if the user does change their password, they are still not logged on and the api call continues to fail. (they can log on normally directly, just not via our SSO link)
Is there documentation that can shed light on this?
/Michael Turner
directnic
Password & Security
Change Password
page
It is invalid in the sense that, if the user does change their password, they are still not logged on and the api call continues to fail. (they can log on normally directly, just not via our SSO link)
Is there documentation that can shed light on this?
/Michael Turner
directnic