I can test sign document with 1 Define Signature
but How to add 2 define signature in XML Tag ?
http://webagentdev.arx.com:88/testApp/
Tab : Define a signature field
Thank you for advance
[Disclosure: I work for CoSign]
In response to your question, our engineering group has investigated the issue. For the current release (ver 7.2), the CoSign Web App product, via its Web Agent API, will only create one signature field. The <SigProfiles> element should only contain, at most, one <SigProfile> child element.
Creating multiple Signature Fields
The Web Agent can handle multiple signature fields, the issue is how to create them. We recommend using the CoSign Signature SOAP API
Another advantage of using the CoSign Signature SOAP network api is that it enables you to position the signature fields by using Locator Tags instead of using specific xy positioning. See the method SAPISignatureFieldLocatorEnumInit available via the CoSign Signature SOAP Sign call.
Related
I'm using Swashbuckle.AspNetCore to generate swagger and include the Swagger UI with my Web API project.
In order to mask a password field's entry, I implemented an ISchemaFilter as described here. (Basically it just adds "format": "password" to the field's schema in the swagger.json.)
This works for field entry:
...but after I send the request, the password is displayed in plain-text:
How can I hide the password text in these fields?
Swagger UI does not mask passwords or API keys in the generated cURL commands. As one of the developers explains:
think of the cURL command as a way to repeat the exact network request that happened in Swagger UI, outside of the UI
So there's no way to fully mask the passwords, apart from forking Swagger UI and implementing this functionality yourself.
On a side note, never send passwords in the query string. Send them in the request body instead.
I have automated the use of Docusign from an Access Database using https calls from VBA
Now I have to change from their legacy authentication to use OAuth 2.0
I need to create a JWT and then use this to exchange for a Docusign API Access Token
I can create and encode the Header & Payload but need to generate the Signature part by encoding the Header and Payload to Base64 (which I can do) but then need to use the Private Key (also have a Public Key) which I have from Docusign and use something like RSASHA256 (as per JWT.io) to generate the Signature to add to my JWT
Does anyone know how I can create this signature element from VBA please
Thank you
you could try some of this code (part of a repository I made): https://github.com/krijnsent/crypto_vba/blob/master/ModHash.bas
You do need .NET 3.5 or greater on your system, as it's used by the hashing algorithms (System.Security.Cryptography).
We are developing for one of your customers a method from our application (written exclusively in LiveCode Script) and need to utilise SOAP via a POST command directly from LiveCode. I eventually, after a lot of digging into the resources pages, found some reference on how to Post 'CreateAndSendEnvelope' from here:
CreateAndSendSchema
However, it does not show where to place login credentials for the user or company or whatever so that it is attributed to the correct account.
I found this question here which kind of points me in the right direction, but do you not have any specific documentation on how to set up your headers and body when using XML for both authenticating and sending a document via email using SOAP?
Providing a simple guide demonstrating the header required and the basic XML to POST to send a document with tags for signing to a single recipient by email using a senders user credentials would be perfect.
Thanks
Sean.
Pi Digital Productions Ltd
SOAP is still using what we call "Legacy Auth" which is the older, less secure, (not OAUTH) authentication.
To use that, you still need an IK (Integration Key) but you provide the username, password and IK in clear text inside a header called X-DocuSign-Authentication that looks like this:
'X-DocuSign-Authentication: { "Username":"DocuSign#example.com", "Password":"DocuSign_password", "IntegratorKey":"DocuSign_Integrator_Key" }'
Currently we're generating Swagger 2.0 documentation using Swashbuckle.AspNetCore. The authentication mechanism being used requires three headers:
X-API-KEY: The shared key
X-API-SIGN: Signature of the request composed of HMACSHA256 hashed value of Hashed secret, Timestamp, Method, Endpoint, and Body
X-API-TIMESTAMP: This is the same timestamp used in the signature
I don't think Swagger or Swashbuckle support this natively so I would likely need to set up some javascript to fill in hidden fields or something in the swagger docs.
I'm currently using an OperationFilter to prepend operation parameters to each request. This doesn't help me once the page loads though since the user will need to enter their API key and secret, which everything else is calculated based on. Clearly javascript will be required here.
Can anyone provide suggestions for how to handle this cleanly?
I wanted to put this as a comment but comments do not allow format so here you go:
The Swashbuckle.AspNetCore seems to be missing the InjectJavaScript feature:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/search?l=C%23&q=InjectJavaScript
It is there on the older project:
https://github.com/domaindrivendev/Swashbuckle/search?l=C%23&q=InjectJavaScript
That is what I've used to inject some javascript, without that we are very limited.
Now looking at this from a different perspective:
It seems you want to embed the authentication process on the swagger ui...
Maybe on the backend you should bypass the authentication if the request comes from Swagger-Ui
We already have an API with the URI as Post/v1/payees used for the functionality to add payees. Another API has to be designed for this functionality but in this API only the control flow id shall need to be sent instead of all the fields required for adding the payee. The required fields shall be taken from cache for this API. Please help in suggesting the name for this API.