Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics

Hello there,  I do not believe we ( Vancity ) are using PCC ( Personal Certificate Client ).  Please provide your confirmation.

After doing some 11.39 SANDBOX testing; seems retrieving Sender via Email works but retrieving Sender via Sender ID does not.

Sender sdr = new Sender();
AccountService accountService = new AccountService();
sdr = accountService.GetSender("##########");

We are getting an intermittent service connection error when generating tokens,  do you have any ideas what would cause this issue?

Replies Created

Reply to:

0 votes

You seem to have been able to "paste" the info directly in which didn't work for me so I tried to save/attach a couple of image files. One is a portion of the Evidence Summary and some body details for POST /api/authenticationTokens/signer/multiUse

The body is below as well, "??????" I can't seem to find value for signerId that works and tried many values. The packageId is fine.  I see where you have differentiated ID for Roll vs ID for Signer but I don't know what signerId is called / referred to as in the APP it self, where can I see it in the App, by what label/text description? or is it even visible in App ( as in how a users sees it )?

{
  "packageId": "KPK77FQHcXjr5xZJ5bq9lRefZZM=",
  "signerId": "??????",
  "sessionFields": {},
  "value": "string"
}

 


Reply to: GET /api/account/senders/{senderId}

0 votes

When you say "Sender ID is generated by OneSpan Sign system when the sender was invited."  I thought the "sender" does the "inviting" i.e. "sender" sends Email to "recipient" (inviting) them to sign documents in question.  Who? invites a "sender". . .


Reply to: 400 Bad Request error using POSTMAN

0 votes

I went back to try a new clientId and secret via US sandbox. POSTMAN allows you to indicate "Auth" TYPE but I'm not sure which I s/b using, perhaps Bearer Token, or OAuth 2.0, or No Auth.  I tried various options but still got 400 error. I notice POSTMAN has it's own Token in it's own header field

08:01:31.984 (Vancouver Time PST) 03Jul2020 

POST https://sandbox.esignlive.com/apitoken/clientApp/accessToken
400
344 ms
Network
Request Headers
Accept: application/json
Content-Type: application/json
Postman-Token: 8d2211fe-9b1a-4048-8ff0-0139a0944975
Request Body
{
  "clientId": "173??????????????88120d007e",
  "secret": "6879??????????????????????????????????????????????????????????????????8480",
  "type": "OWNER"
}
Response Headers
Server: nginx
Date: Fri, 03 Jul 2020 15:01:32 GMT
Content-Type: text/html
Content-Length: 150
Connection: close
Allow: GET, POST, HEAD, PUT, PATCH, DELETE
Response Body
<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>


Reply to: 400 Bad Request error using POSTMAN

0 votes

Duo, can you confirm your results are using POSTMAN with auth = "No Auth"  (and clientId, secret in Body/Payload).  Do you get a new token in the response body?


Subscriptions

Topics Replies Freshness Views Users

Hello there,  I do not believe we ( Vancity ) are using PCC ( Personal Certificate Client ).  Please provide your confirmation.

1 4 months 3 weeks ago 37

After doing some 11.39 SANDBOX testing; seems retrieving Sender via Email works but retrieving Sender via Sender ID does not.

5 1 year 9 months ago 29

Sender sdr = new Sender();
AccountService accountService = new AccountService();
sdr = accountService.GetSender("##########");

5 1 year 9 months ago 37
5 6 months 2 weeks ago 86

We are getting an intermittent service connection error when generating tokens,  do you have any ideas what would cause this issue?

3 2 years 1 month ago 50

Code Share

This user has not submitted any code shares.