This topic contains 1 reply, has 2 voices, and was last updated by  Duo_Liang 3 months ago.

  • Author
  • Participant
    Member since: 29.01.2016
    Number of posts: 18

    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 “”, 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):

    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.

    Below is a sample JSON payload.

    Note we are also seeing this with the Java SDK.

    “name”: “Customizing Signing Ceremony”,
    “settings”: {
    “ceremony”: {
    “events”: {
    “complete”: {
    “dialog”: false,
    “redirect”: “”
    “inPerson”: true,
    “declineButton”: true,
    “declineReasons”: [],
    “disableDeclineOther”: false,
    “disableDownloadForUncompletedPackage”: false,
    “disableFirstInPersonAffidavit”: true,
    “disableInPersonAffidavit”: false,
    “disableOptOutOther”: false,
    “disableSecondInPersonAffidavit”: true,
    “documentToolbarOptions”: {
    “downloadButton”: true
    “handOver”: {
    “title”: “You will be redirected to Google homepage”,
    “href”: “”,
    “text”: “Exit to site”
    “hideCaptureText”: false,
    “hideLanguageDropdown”: true,
    “hidePackageOwnerInPerson”: true,
    “hideWatermark”: true,
    “maxAuthFailsAllowed”: 3,
    “optOutButton”: true,
    “optOutReasons”: [
    “Decline terms.”
    “style”: null,
    “layout”: {
    “footer”: {},
    “navigator”: true,
    “brandingBar”: {
    “logo”: {
    “src”: “”,
    “link”: “”
    “header”: {
    “feedback”: true,
    “globalActions”: {
    “confirm”: true,
    “download”: false,
    “hideEvidenceSummary”: false,
    “saveAsLayout”: false
    “titleBar”: {
    “title”: true,
    “progressBar”: true
    “breadcrumbs”: false,
    “globalNavigation”: false,
    “sessionBar”: true
    “documents”: [
    “approvals”: [
    “id”: “ExampleSignatureId”,
    “role”: “Signer1”,
    “fields”: [
    “page”: 0,
    “top”: 200,
    “subtype”: “LABEL”,
    “height”: 50,
    “left”: 100,
    “width”: 200,
    “id”: “myLabelField”,
    “type”: “INPUT”,
    “value”: “Example label field value”
    “page”: 0,
    “top”: 100,
    “subtype”: “FULLNAME”,
    “height”: 50,
    “left”: 100,
    “width”: 200,
    “type”: “SIGNATURE”,
    “name”: “ExampleSignatureId”
    “name”: “”
    “id”: “sample-contract”,
    “name”: “Test Document”
    “status”: “SENT”,
    “type”: “PACKAGE”,
    “roles”: [
    “id”: “Signer1”,
    “type”: “SIGNER”,
    “signers”: [
    “email”: “”,
    “firstName”: “John”,
    “lastName”: “Smith”,
    “id”: “Signer1”
    “name”: “Signer1”
    “name”: “Example Package”

    • This topic was modified 3 months ago by  serg.
    • This topic was modified 3 months ago by  serg.
    • This topic was modified 3 months ago by  serg.
    Member since: 14.06.2018
    Number of posts: 767



    Hi serg,

    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!


    Duo Liang
    OneSpan Junior Technical Evangelist

You must be logged in to reply to this topic.