SmartERP Documentation An Ashewa Technology Solutions Platform

Cryptographic Architecture, X.509 Certificates & SHA-256 Hashing

Technical deep dive into the PDF cryptographic engine, SHA-256 document hashing, RSA public-key infrastructure, and digital seals.

1. Overview & Business Value#

SmartERP Sign secures every signed document using public-key cryptography implemented in addons/smarterp_sign/utils/crypto_engine.py.

Module map showing dependencies between SmartERP Supply Chain Core, Tenders, Store Vouchers, Landed Costs, and WMS.
SmartERP Supply Chain and Sourcing architectural module map.

SmartERP Application Interface and Dashboard

1. Cryptographic Hash Integrity#

Prior to signature capture, the system computes the cryptographic SHA-256 digest of the source PDF. Each participant's signature, timestamp, IP address, and identity token are appended as an immutable incremental update to the PDF specification (ISO 32000-1).

$$H = \text{SHA-256}(\text{Original PDF} \parallel \text{Signer Signature} \parallel \text{Timestamp})$$

Any subsequent alteration to the PDF invalidates the cryptographic signature immediately.

2. Prerequisites & Access Permissions#

  • Required Modules: smarterp_sign, base, web
  • Security Group: Internal User (Technical ID: base.group_user)
  • Master Data Dependencies: Established corporate settings, defined role permissions, and active records.

3. Step-by-Step UI Execution & Verification#

Step 1: Navigating to the Module Interface#

  1. Access your SmartERP instance at https://smarterp.et/odoo.
  2. Open the main App Switcher and select the operational application.
  3. Select the target view or configuration form.

Step 2: Executing Transactional Operations#

  1. Fill in required parameters according to institutional procedures.
  2. Validate entries and confirm execution.
  3. Review updated record state in the chatter audit trail.

4. Advanced Configuration Points#

  • Automated Tasks (Crons): Dedicated background crons manage recurring tasks and state transitions.
  • Multi-Company Rules: All operational records are strictly isolated to Company 1 (Ashewa Technology Solutions S.C.).

5. Comprehensive Troubleshooting Matrix#

Symptom / ErrorProbable Root CauseResolution Action
Access Rights Error: Operation not allowedUser lacks required operational permissions.Assign user to the designated security group under Settings → Users.
Document state locked or read-onlyTransaction is in validated or closed state.Reopen document if permitted or contact designated manager.
Last updated: 2026-11-15