The CodeB Identity Broker, a leader in identity management and security solutions, has integrated the timestamp method from the Cloud Signature Consortium API, enhancing its ability to assure the integrity and authenticity of digital content through the generation of timestamp tokens.

Understanding the Timestamp Method #

The timestamp method is crucial for generating timestamp tokens for a given hash value, essential for establishing long-term validation digital signatures and facilitating accurate billing operations. This method can be executed directly by the Remote Signature Service Provider (RSSP) or by a connected Time Stamping Authority, offering pre-configured timestamp services and eliminating the need for signature applications to seek timestamp services from different providers.

Enhancements in CodeB Identity Broker #

The CodeB Identity Broker now provides an RFC 3161 compliant timestamping service at the endpoint <BaseURL>/tsa. A demo server for this service is accessible at https://nfcsign.com/tsa, allowing users to experience the service and understand its functionalities.

How to Use “signatures/timestamp” Method #

Understand the Purpose #

• The method is used to generate a timestamp token by the RSSP or by a connected Time Stamping Authority, providing pre-configured timestamp services.

Prepare Input Parameters #

• hash (REQUIRED): Base64-encoded hash value to be timestamped.
• hashAlgo (REQUIRED): OID of the algorithm used to calculate the hash value.
• nonce (OPTIONAL): A unique, large random number, represented as a hex-encoded string.
• clientData (OPTIONAL): Defined in the Input parameter table in section 8.3.2.

Send the Request

• Construct and send a request to the API endpoint with the prepared input parameters, ensuring the correct format and inclusion of all required parameters.

curl -X POST
 -H "Content-Type: application/json"
 -H "Authorization: Bearer <token>"
 -d '{
          "hash":"sTOgwOm+474gFj0q0x1iSNspKqbcse4IeiqlDg/HWuI=",
          "hashAlgo":"2.16.840.1.101.3.4.2.1",
          "nonce":"234242",
          "clientData":"Hello World"
     }'
https://nfcsign.com/signatures/timestamp

Handle the Output

• The method returns the timestamp token as a Base64-encoded string in the “application/json” format.
• If the nonce parameter is included in the request, it should also be included in the timestamp token.

Handle Error Cases

• Handle specific error codes and descriptions returned by the API for various error cases, such as missing or invalid parameters, and invalid request format.

Use the Timestamp Token:

• Use the received timestamp token as needed, for example, to prove the existence of specific data at a certain point in time.

Enhanced Security and Integrity #

The integration of the timestamp method at <baseURL>/signature/timestamp and the availability of an RFC 3161 compliant timestamping service at <baseURL>/tsa enhance the security and integrity of digital content managed by the CodeB Identity Broker. Users can verify the received timestamp token to ensure its integrity and authenticity.

Reliable Timestamping Service #

The inclusion of an RFC 3161 compliant timestamping service in the CodeB Identity Broker, along with Aloaha / CodeB’s longstanding support for RFC 3161 through their Time Notary service, offers users reliable and diverse options for securing their digital content and transactions.

The integration of the timestamp method and the introduction of an RFC 3161 compliant timestamping service in the CodeB Identity Broker represent significant advancements in digital content security and integrity. The enhanced CodeB Identity Broker is a robust solution for modern security needs, catering to legal documents, financial transactions, and other forms of digital data, with a demo available at https://auth.aloaha.com/signature/timestamp and https://auth.aloaha.com/tsa for users to explore its advanced capabilities.

Further questions? Just contact info@aloaha.com