SmartTSA allows administrators to generate and install digital certificates that enable the appliance to operate as a trusted Time Stamping Authority (TSA).
SmartTSA supports the issuing and revocation of digital certificates for Timestamping Service Units.
These certificates are used by SmartTSA to:
- Digitally sign timestamps
- Provide trusted proof of existence at a given time
- Enable compliant TSA operations
Each Timestamping Service is associated with a certificate stored securely inside the HSM.
SmartTSA supports two main approaches for certificate management:
With internal Certificate Services:
- The organization manages certificate lifecycle directly
- SmartTSA handles:
- Creation
- Expiration
- Revocation
- Self-enrollment
This approach is suitable for:
- Internal deployments
- Test environments
- Private PKI infrastructures
With an external trusted authority:
- Certificates are issued by an official CA
- The CA manages:
- Trust chain
- Certificate validation
- Public compliance
This approach is mandatory for:
- Regulated TSA services
- Publicly trusted timestamping infrastructures
- eIDAS-compliant deployments
Regardless of the approach, the process includes three mandatory steps:
- Create a certificate request
- Submit the request to a CA or self-enroll
- Process and install the certificate to enable a Timestamping Service
To create a TSA certificate request:
- Log in to the SmartTSA Administrative Console
- Select from the left menu:
Generate Certificate RequestA form will be displayed.
The administrator must fill in certificate attributes, including:
A mnemonic name assigned to the service.
Example:
Test_TSA
Available options:
- MD5
- SHA-1
- SHA-256
⚠️ Recommended for production:
- SHA-256
Available key sizes:
- 1024 bits
- 2048 bits
The key pair is generated securely inside the HSM.
⚠️ Recommended:
- 2048 bits (minimum enterprise standard)
Other mandatory fields include:
- Country
- Organization
- Common Name
- Locality
- Additional X.509 attributes
After completing the form:
- Click:
Generate RequestThe request is created and becomes pending for validation.
To process generated requests:
- Select from the left menu:
Manage Pending Certificate RequestsA table will list all requests awaiting validation.
Each pending request supports the following actions:
Displays a summary of request data, including:
- Subject information
- Key parameters
- Request identifier
Allows downloading the request in:
.pemformat
This is required when forwarding the CSR to an external CA.
Procedure:
- Click Download
- Select destination folder
- Send the CSR to the trusted authority
After the CA issues the signed certificate:
- Select:
Assign certificate- Upload the CA-issued certificate file
This binds the trusted certificate to the request.
Result:
- The request becomes an Offline Timestamping Service
SmartTSA can self-sign the request internally.
- Select:
Self-enrollResult:
- A self-signed certificate is generated
- The service is created as Offline
⚠️ Not recommended for regulated production TSA deployments.
Allows removal of unused or incorrect requests.
- Select:
DeleteUse carefully, as deletion cannot be undone.
Once a certificate is assigned or self-enrolled:
- SmartTSA creates a Timestamping Service
- The initial status is:
OfflineThe service must be explicitly activated.
To activate the service:
- Locate the service in the list
- Select:
Modify- Change status from Offline to:
OnlineOnce online, the TSA service begins issuing timestamps.
Each Timestamping Service can be exposed with a URL suffix.
Example:
Base appliance URL:
http://XXX.XXX.XXX.XXX
Service suffix:
/TSAtest
Final service endpoint:
http://XXX.XXX.XXX.XXX/TSAtest
This allows multiple TSA services to coexist on the same appliance.
The service certificate can be downloaded via the service list using:
DownloadThis is useful for:
- Client integration
- Trust store configuration
- Audit documentation
For enterprise TSA deployments:
- Always use CA-issued certificates in production
- Use SHA-256 and 2048-bit keys minimum
- Keep services Offline until fully validated
- Document certificate lifecycle operations
- Monitor service status continuously