Creating a signing URL without authentication

Have you tried creating a session URL with: SessionToken sessionToken = eslClient.SessionService.CreateSessionToken(packageId, signer); And using the returned sessionToken in the url: https://sandbox.esignlive.com/access?sessionToken={Your Token} That will allow you to jump straight into the session without entering the SMS code. If you use the GetSigningURL or whatever that call is, you DO have to enter the SMS. Using the sessionToken will allow you to go around the eSignLive authentication. Hope this helps.

I read here http://docs.e-signlive.com/doku.php?id=esl:e-signlive_guide_sessions that session tokens are only good for 20 mins. Our customer needs an indefinite time because they could have someone use this 5 mins after creation or 6 hours later. Is it possible to turn off the 20 min limit?

Being that this method does go around the authentication methods, I would recommend simply creating a new session for the user to use, on demand, when they want to access it. You can create a new session to an existing package at any time. So, when a user logs in, to access their signature session, you'd simply create a new session for them, at that time. This way, no matter when they come in, you're able to provide them with a current session.

Ok I will relay this information. One more questions. The URL that you append the session token too http://.com/access?sessiontoken={0} will it always be "/access?sessiontoken={0}" even if they have a Silanis server at their location or can they change that?

I would guess that would always be the url extension, but I am not 100% on that. Let me look into it and get back to you.

Any update if the URL concatenation will be the same if the person has a Silanis server on premise?

Sorry. The response I got was that you cannot directly change it, but you could probably use Apache rewrite to handle it. May I ask why you're wanting to change this?

Haha no I do not want to change this. However I know some customers like to have their things set a certain way so I was just curious. It was just an attempt to be ready in case someone else does.