amine_desjardins | Posts: 11

Create signerAuthenticationToken

0 votes

Hello I found this code for to be able to create a signing session : 

 

 Map<String, String> signerSessionFields = new LinkedHashMap<String, String>();
        signerSessionFields.put("Transaction ID", "1234567890");
        signerSessionFields.put("Login Token", "8888888888888");
        final String signerAuthenticationToken = eslClient.getAuthenticationTokensService().createSignerAuthenticationToke (packageId.getId(), "signer1", signerSessionFields);
        System.out.println("https://sandbox.esignlive.com/access?sessionToken=" + signerAuthenticationToken);

 

My question, how I can get the login token that I will use in signerSessionFields ?? 

Thanks 


Duo_Liang | Posts: 3776

Reply to: Create signerAuthenticationToken

0 votes

Hi Amine,

 

Unfortunately, you can only specify session fields when generating Authentication Token, not Login Token.

May I know the reason why you want to add session fields? Could you also clarify your business requirement a little bit?

 

Duo

 

 


amine_desjardins | Posts: 11

Reply to: Create signerAuthenticationToken

0 votes

Allo Duo Liang 

We want to have signing sessions without going through authentication questions (sms, challenge, etc.)

For internal signatories (who have an email from our company), we managed to have a single-use url, with a token that allows us to authenticate and sign without going through authentication ceremonies (sms, challenge, etc.) we connect with the session of our company email

Now, we have signatories who do not have sessions already open with a company email, we want them to be able to sign with a session created from their accounts (user accounts of our application). One of your representatives offered us this solution, that's why I wanted to know how to get the Login Token to create the session


Duo_Liang | Posts: 3776

Reply to:

0 votes

Hi Amine,

 

I see. If you don't want signatories to go through authentication questions, then you'd still use Signer Authentication Token, not Login Token.

There are two types of signing links, respectively combined by Authentication Token and Login Token:

https://sandbox.esignlive.com/access?sessionToken={signerAuthToken}

And

https://sandbox.esignlive.com/auth?target=https%3A%2F%2Fsandbox.esignlive.com%2Ftransaction%2F0q5SoDJjyLpD3wspCHTlZlQkTCk%3D%2Fsign&loginToken=UXNxxxxxT3padz09

 

Main differences between them are:

1. Authentication Token is short-lived (e.g. 30 minutes) while Login Token won't expire

2. Authentication Token is more secure than Login Token, hence signatories won't need to go through authentication questions.

3. As stated above, you can ONLY specify session fields to authentication token since it's session based and expires

4. Signing URL combined with Login Token is exactly the link behind the "Go to Document" link in the activation email

 

Duo

 


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off