Has anyone noticed problems with the handover URL and hash location strategy routing? If so, have you found a workaround?
When setting the handover url to something like “https://www.mydomain.com/#esign”, we are seeing different behavior between the handover button and text link. The parameters that OneSpan Sign injects into the URL are in two different locations:
ButtonLink (generated via JQuery): https://www.google.com/#esign?package=sTXJEk1Qh3gRLErofZH26xiDYkI%3D&signer=Signer1&email=me%40myemail.com&status=SIGNER_COMPLETE
The ButtonLink has the correct URL, however, for the Text Link the URL is wrong. The parameters are injected between the end of the baseURL (domain) and the # (hash), which confuses our Angular routing, which is using HashLocationStrategy.
Has anyone else seen this? Are there any known workarounds other than avoiding HashLocationStrategy, which we are looking into, however, configuration and testing impacts are impeding progress and it now involves multiple internal teams.
We have already realized this inconsistent behavior, and R&D team is investigating into the issue. It won’t take long before some result comes out and then I will updated this thread.
Thanks for posting!