LogoLogo
  • Introduction
  • Getting Started
  • SenseCrypt Server
    • Starting the server
    • Configuration
    • Licensing and Authorization
    • Using the Swagger Docs page
    • Authorization
    • Using a JWT Token for Mobile Authorization
    • Getting information about your license
    • SenseCrypt eID
      • Generating your first SensePrint eID QR
      • Generating a raw SensePrint
      • Decrypting a raw SensePrint
      • Parsing a SensePrint
    • SenseCrypt Face PKI
      • Configuration
      • Accessing your Root Certificate
      • Generate your first Face Certificate
      • Verifying a Face Certificate
      • Encrypting Data/Keys using a Face Certificate
      • Face Decrypting Data/Keys
      • Face Signing
      • Face Signature Verification
    • Accessing the server for testing
    • Liveness Image Requirements
  • SenseCrypt Mobile SDKs
    • Licensing
    • Authorization for Online SDKs
    • Liveness and Face Capture
    • Android SDK
    • iOS SDK
  • Conclusion
  • FAQ & Search
  • Appendix
    • Privacy Preserving Biometric Verifiability
    • Principles of Privacy Preserving Face Verification
    • Foundational vs Functional eID
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. SenseCrypt Server

Licensing and Authorization

Information about licensing and authentication for the server

PreviousConfigurationNextUsing the Swagger Docs page

Was this helpful?

The licensing for the server is governed by a license file called server.lic. This file is located in the root folder of the distribution bundle.

The server.lic file determines quotas and limits for the system. During development, the initial file should provide enough quotas for your needs. As you approach a production deployment, please contact Seventh Sense for a review of your quota needs.

When the server is running, it offers several end-points that can be called via HTTP clients in a language of your choice.

It is to be noted that these end-points are meant to be accessed via server-to-server calls. If you wish to access similar functionality from mobile, you can use the SenseCrypt Mobile SDK Online which includes secure access to the functionality provided by the server end-points.

To access these server end-points for server-to-server API calls, please use your api_key

A random API key was included in the secrets.json file mentioned in the previous section. Including it in requests using the x-api-key header will help authorize your requests. This is only recommended for server-to-server calls.

For the mobile SDKs, you have the option of authenticating via the mobile_api_key, or if you want to implement your own authentication, you can first use your api_key in a server-to-server API call to . Then, you can .

generate a JWT token
use the generated JWT token in the mobile SDKs