Use cases in SDK.finance

PostgreSQL

SDK.Finance does not use the crypto library directly.
All usages of this library are performed by the DB system itself for their own needs.
Only Secure Client Connections is used

MongoDB

SDK.Finance does not use the crypto library directly.
All usages of this library are performed by the DB system itself for their own needs.
Only Secure Client Connections is used

Kafka

SDK.Finance does not use the crypto library directly.
All usages of this library are performed by the DB system itself for their own needs.
Only Secure Client Connections is used

Backend

The following scenarios of the crypto usage are implemented in the backend system:

• HTTPS/TLS Encryption for the REST API server (Tomcat)
  The default cipher suite configuration is:

  • TLS 1.2:

    • TLS_AES_128_GCM_SHA256

    • TLS_AES_256_GCM_SHA384

    • TLS_CHACHA20_POLY1305_SHA256

  • TLS 1.3:

    • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

    • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

    • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

    • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

• Message Digests and Integrity

  • Hashing user password
    Algorithm: SHA256-WITH-RSA

  • Hashing coin PIN
    Algorithm: SHA256

  • Hashing a JWT token
    Algorithm: SHA256

• Digital Signatures

  • Sign requests to providers if required
    Algorithm: various (depending on the provider requirements).
    Mostly used: SHA256withRSA