Within our OneSpan build, we have chosen to use optional signatures where a document may have more than one section to sign but a customer has a choice which sections they are approving (e.g. service work order). This has been working well until an edge case appeared in testing.
Receiving Access Denied on Interactive API Reference Page. Occurs whether logged in or out. Previously don't think the page was behind authentication at all. Already cleared browser cache, using multiple browsers etc. How to fix?
https://app.screencast.com/HAJgXOKfux8wM
In looking at the API reference as well as playing around with the calls in Postman, while Onespan guides users to create a bearer token, often they're not using it, instead passing the API Key in basic authentication. Why is this? What is the best practice generally on what authentication method to use? As elsewhere I presume bearer token method is superior but unable to determine whether it's always supported throughout OS REST API?
Thank you!
Hey,
So when I use OneSpan sign as myself (connected user to onespan in Salesforce under admin tab) I have no issues. But if I have another admin who has same permissions try to view a transaction record they get the Insufficient Privileges error. Any idea why this is happening?
Hi,
I have a method to Retrieve the attachment:
public async Task<byte[]> GetAttachmentContentAsync(string packageId, string attachmentId)
{
_httpClient.DefaultRequestHeaders.Accept.Clear();
_httpClient.DefaultRequestHeaders.Accept.ParseAdd("application/pdf");
Our api encounter multiple issues when update role email
e.g: [email protected] is considered invalid for onespan api
Could you clarify which type of email validation onespan api does? Beaucase it seems this is a false positive validation
If you do some kind of weird or special email regex validation, it would be very helpful if you can provide a javascript regex compatible with some samples where pass and fails
Duo,
Has anything changed with the process of changing the notary on a package? We are now not able to change the Notary at all on any of our Notary packages. Also, just fyi, this happens when trying to use a notary that is within the senders account.
Let me know. :)
Guys,
I am getting this error when trying to update the package status of a package. Is there something going on with the PUT call? I am able to do the other POST calls.
url - https://sandbox.esignlive.com/api/packages/{transactionID}
We’ve seen an error a few times in the past week or so (screenshot attached.) During signing, after clicking Confirm on one doc we get a server error as below. We have to close the modal and restart signing, which picks us up at the document we were meant to go to next but I’m unclear why we are starting to see these errors. The error is very random and doesn't occur every time.
Hi There,
I have a use case where I need to retrieve information around user creation/user deactivation and user role (s) via API's and integrate with my SIEM solution. Is this possible?
Thanks,
Calum