Source
Signer identification — found from sitemap — OneSpan Sign
Checked for OneSpan Sign on 10 Nov 2026
- Page
- https://docs.onespan.com/docs/external-signer-verification
- Checked
- 10 Nov 2026, 08:48 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:29ff62a3110c517aafd4cc820bb26cd5fc3bf5e4df43e79a61d0f4cab56e3462
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
External signer verification Report an error
“When a signer is trying to confirm their approval of a document within OneSpan Sign, it is sometimes desirable for the system to verify the signer's identity via their credentials with an external organization (e.g., credentials from Validated ID, Asseco, or DIGIPASS).”
-
Java SDK integration Report an error
“A Java SDK enables this kind of "external signer verification" by integrating the OneSpan Sign Application Backend with an external organization’s Verification Server.”
-
SDK topics Report an error
“The following topics explain how to use that Integration SDK: Sequence Diagram Sample Integration Code”
-
Intended audience Report an error
“The intended audience for this information is any developer who has a good knowledge of an External Verification Provider that they want to integrate with the OneSpan Sign Application Backend. The developer doesn't need any detailed knowledge of the communication protocol between the External Verification Server and the OneSpan Sign Application Backend.”
Scores citing this record
- The Data Protection Officer Signer identification
- The HR Operations Lead Signer identification
- The Integration Engineer Signer identification
- The Legal Counsel Signer identification
- The Revenue Operations Lead Signer identification
- The Skeptic Signer identification