 | Session Class |
A session to a cryptographic device (HSM, USB token, etc.) to perform cryptographic operations
The session can be used to create signature configuration to sign documents.
To acquire a session, the following steps must be performed:
- Load the PKCS#11 driver module using Load(String).
- Get the appropriate cryptographic device from the module's Devices. If it can be assumed that there is only a single device available, the GetSingle can be used.
- Create a session to the device using CreateSession(String).
Inheritance HierarchyPdfTools.InternalNativeBase
PdfTools.InternalNativeObject
PdfTools.Crypto.ProvidersProvider
PdfTools.Crypto.Providers.Pkcs11Session
Namespace: PdfTools.Crypto.Providers.Pkcs11
Assembly: PdfTools (in PdfTools.dll) Version: 1.7.0+cfcc11b476b3e1eb4320f0f37269191f64e36bd8
Syntaxpublic class Session : Provider
The Session type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | Certificates | The cerfificates of the device The certificates available in this device. Note that some certificates or their private keys (see HasPrivateKey) might only be visible after Login(String). |
| TimestampUrl | The URL of the trusted time-stamp authority (TSA) from which time-stamps shall be acquired The TSA must support the time-stamp protocol as defined in RFC 3161. The property’s value must be a URL with the following elements: http[s]://[‹user›[:‹password›]@]‹host›[:‹port›][/‹resource›] Where:
Applying a time-stamp requires an online connection to a time server; the firewall must be configured accordingly. If a web proxy is used (see Proxy), make sure the following MIME types are supported:
|
Methods| Name | Description | |
|---|---|---|
 | CreateSignature | Create a signature configuration based on signing certificate |
| CreateSignatureFromKeyId | Create a signature configuration based on the private key's ID and an external certificate Create a signature configuration where only the private key is contained in the PKCS#11 device and the signing certificate is provided externally. This is intended for PKCS#11 devices that can only store private keys, e.g. the Google Cloud Key Management (KMS). The private key object is identified using its ID, i.e. the CKA_ID object attribute in the PKCS#11 store. The certificates of the trust chain should be added using AddCertificate(Stream). |
| CreateSignatureFromKeyLabel | Create a signature configuration based on the private key's label (name) and an external certificate Create a signature configuration where only the private key is contained in the PKCS#11 device and the signing certificate is provided externally. This is intended for PKCS#11 devices that can only store private keys, e.g. the Google Cloud Key Management (KMS). The private key object is identified using its label, i.e. the CKA_LABEL object attribute in the PKCS#11 store. The certificates of the trust chain should be added using AddCertificate(Stream). |
| CreateSignatureFromName | Create a signature configuration based on certificate name |
| CreateTimestamp | Create a time-stamp configuration Note that to create time-stamps, the TimestampUrl must be set. |
| Dispose | Close the object Release all resources associated with the object.(Inherited from Provider) |
| Equals | (Inherited from NativeObject) |
| GetHashCode | (Inherited from NativeObject) |
| Login | Log in user into the cryptographic device Login is typically required to enable cryptographic operations. Furthermore, some of the device's objects such as certificates or private keys might only be visible when logged in. Note that many devices are locked after a number of failed login attempts. Therefore, it is crucial to not retry this method using the same password after a failed attempt. |
See Also