News for hackers. Stuff that matters.
Re:Lessons from Failed DocuSign Integration by inoda on Thursday January 24, 2019 @12:48PM (#18990987)
Yes. The problem is that on page refresh, that constraint is lost and the user is logged into the account, in DS UI. They can click around anywhere at this point, outside of the page we specified.
Re:Lessons from Failed DocuSign Integration by Bamafan on Thursday January 24, 2019 @01:02PM (#18991128)
I'm curious as to how HelloSign guards against this. Do they have some sort of session token that sends you back to the signing page on refresh? (i.e. similar to guard to avoid submitting shopping cart purchases twice).
Re:Lessons from Failed DocuSign Integration by inoda on Thursday January 24, 2019 @01:20PM (#18991319)
HelloSign's embedded signing happens in a iframe, through their JS client. The user is never directed to HelloSign's site unless you choose to to an un-embedded workflow.
Re:Lessons from Failed DocuSign Integration by treis on Thursday January 24, 2019 @01:05PM (#18991163)
>The problem is that on page refresh, that constraint is lost

Why can't you put this constraint in a session and pass it back in on refresh?

Re:Lessons from Failed DocuSign Integration by inoda on Thursday January 24, 2019 @01:18PM (#18991301)
View 1 is on the DS domain. We have no control once the user is in there aside from giving the redirect URL.
Re:Lessons from Failed DocuSign Integration by treis on Thursday January 24, 2019 @01:31PM (#18991444)
This is the point where someone is extremely confused but I'm not sure which one of us it is.

My understanding is that you have a page at the end of some process for the user to sign a document. The first time the user goes to the page they see the screen to sign something (View 1). They refresh the screen. Now they see some dashboard like screen where they can see everything (View 2).

Is that not right?

Re:Lessons from Failed DocuSign Integration by inoda on Thursday January 24, 2019 @01:47PM (#18991627)
1. We want the application user to sign a contract.

2. We request an embedded signing url from DS (we provide authentication creds, as well as redirect url as params - what we get back is a "special" url on DS. E.g. it is docusign.com/blahblahblah)

3. We redirect the user to the special DS url.

4. If the user signs, or refuses to sign or w/e, the user will get redirected back to our application via the redirect url we provided in our request on step #2. If the user instead decides to refresh the page, they for some reason are broken out of the signing page, and can now do whatever they want in the account as they are logged into DS's site for some reason.

Re:Lessons from Failed DocuSign Integration by treis on Thursday January 24, 2019 @02:14PM (#18991915)
So you're not embedding the DS page in your site. You're redirecting the user to DS?