Enabling PIV/CAC based signatures through DocuSign within Appian

Appian Max Team — Wed, 08 May 2024 19:27:29 GMT

Current Revision posted to Guide by Appian Max Team on 5/8/2024 7:27:29 PM

This article provides information about utilizing the PIV/CAC signature functionality within a DocuSign integration. If you are unfamiliar with DocuSign integration, it is recommended that you read the Integrating with DocuSign article for information about the key concepts, connectivity with Appian and implementation guidance.

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

Appian Max Team — Tue, 23 Apr 2024 13:14:44 GMT

Revision 12 posted to Guide by Appian Max Team on 4/23/2024 1:14:44 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

Kim Day — Tue, 31 Oct 2023 19:06:11 GMT

Revision 11 posted to Guide by Kim Day on 10/31/2023 7:06:11 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Wed, 18 Oct 2023 15:03:52 GMT

Revision 10 posted to Guide by matt.cosenza on 10/18/2023 3:03:52 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Wed, 18 Oct 2023 15:03:07 GMT

Revision 9 posted to Guide by matt.cosenza on 10/18/2023 3:03:07 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Enabling PIV/CAC based signatures through DocuSign within Appian

joel.larin — Tue, 17 Oct 2023 16:20:07 GMT

Revision 8 posted to Guide by joel.larin on 10/17/2023 4:20:07 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Tue, 17 Oct 2023 16:19:05 GMT

Revision 7 posted to Guide by matt.cosenza on 10/17/2023 4:19:05 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Tue, 17 Oct 2023 15:15:51 GMT

Revision 6 posted to Guide by matt.cosenza on 10/17/2023 3:15:51 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

joel.larin — Tue, 17 Oct 2023 14:54:42 GMT

Revision 5 posted to Guide by joel.larin on 10/17/2023 2:54:42 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Tue, 17 Oct 2023 14:48:45 GMT

Revision 4 posted to Guide by matt.cosenza on 10/17/2023 2:48:45 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Tue, 17 Oct 2023 14:48:11 GMT

Revision 3 posted to Guide by matt.cosenza on 10/17/2023 2:48:11 PM

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

matt.cosenza — Tue, 17 Oct 2023 14:45:26 GMT

Revision 2 posted to Guide by matt.cosenza on 10/17/2023 2:45:26 PM

How can I enable PIV/CAC signatures with DocuSign through Appian?

Getting Started

DocuSign Service Account Settings: (Note: You will need to ask someone from DocuSign's support team to enable these settings)

Enable "PIV/CAC signatures"
Enable "signature details within in the signature manifestation".
- Note: This is needed If you want to display signature details in the signature block (i.e. date signed, CAC information, etc.).

Envelope Creation JSON

When sending the JSON to create an envelope within DocuSign for signature, the recipientSignatureProviders block must be included in order to denote PIV/CAC signatures.

The recipientSignatureProviders code block will be located within recipients->signers code blocks
- The parameter:value within the recipientSignatureProviders code block will equal: signatureProviderName: "UniversalSignaturePen_DS_Smartcard_TSP"
If you would like the "date signed" to be added to the document upon signature, you will need to add the dateSignedTabs code block within the tabs section
- Within this code block, you will specify where the signature will show on the page.

Below is an example of the DocuSign envelope creation JSON:

Note: Best practice is to create constants for parameters but were kept in plain text for this example.

User Experience

Note: if implemented correctly, the entire user experience with DocuSign will take place within Appian.

1. When a user is ready to sign a document, they must insert the PIV/CAC card into the computer. They may be presented with an option to chose which associated certificate they would like to use.

2. After clicking Continue, the user will then be required to confirm the certificate they chose (if there were multiple present)

3. Once the user confirms their identity and finishes the signature, they will then be presented with a box to enter their individual PIN.

4. The document will be officially signed once the PIN has been entered.

Browser Requirements

Chrome:

DocusSign Chrome Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Internet Explorer:

Enable ActiveX Controls: Under the ActiveX Controls and Plug-ins heading, click to enable Initialize and script ActiveX Controls not marked as safe for scripting.

Firefox:

DocuSign Firefox Extension
DocuSign PKI: This must be installed if one needs to digitally sign documents using the signer held certificates.

Tags: integrations

Enabling PIV/CAC based signatures through DocuSign within Appian

joel.larin — Thu, 31 Aug 2023 18:55:04 GMT

Revision 1 posted to Guide by joel.larin on 8/31/2023 6:55:04 PM

TEMP