Authentication Features

Security & Authentication

The CADViewer Conversion Server acts as a powerful REST API and file handler. As such, it includes several flexible authentication mechanisms out-of-the-box to ensure your CAD assets and server endpoints remain secure.

These features are configured within the CADViewer_config.json file.

1. Global Bearer Authentication (API Security)

If your architecture exposes the Conversion Server REST API to external networks or non-trusted microservices, you should enable Bearer Authentication.

When enabled, all API endpoints will reject requests that do not include a matching Authorization: Bearer <token> header.

• globalBearerAutentication: Set to true to enable this feature.
• globalBearerAutenticationToken: Define your secure token (e.g., t-7614f875-8423-4f20-a674-d7cf3096290e).

2. Custom Tenant Bearer Authentication

For multi-tenant systems, or scenarios where different CADViewer front-ends require distinct access profiles, you can specify custom authentication tokens that can be checked by your custom business logic.

• custom_bearerAutentication: Set your secondary/tenant token (e.g., d5d483e8-2f8d-463e-cc01-f41a78b1d94c).

3. File Load Password Authentication

If you are directly loading CAD files via standard URL paths rather than strictly via API blobs, you can protect the file-loading endpoints using Basic Authentication or custom credentials.

• fileLoad_PasswordAuthentication: Set to true to require credentials when fetching files.
• fileLoad_UserName: The required username.
• fileLoad_Password: The required password.

4. JWT & Password Hashing

For advanced implementations involving user sessions, database integration, or dynamic token generation, the server includes robust cryptographic settings for JSON Web Tokens (JWT) and Bcrypt.

• jwtSecretKey: The secret key used to sign and verify JWT tokens across the server (e.g., a45f6g7h8j9k0l193skdlmdj). Ensure this is a strong, cryptographically secure random string in production.
• bcryptSaltRounds: The cost factor for hashing passwords before storing them (default: 10).

5. Azure SAS Tokens (Cloud Storage Integration)

If your infrastructure relies on Azure Blob Storage, CAD files and outputs can be protected via Shared Access Signatures (SAS). The conversion server can automatically append SAS tokens when reading or writing from cloud blobs.

• globalApplicationSasToken: Provide your SAS token string (e.g., ?si=testread1&spr=https&sv=2022-11-02&sr=c&sig=xx).