Authentication:

Authentication is a fundamental aspect of securing communication between users, devices, and DRIVR's APIs. It ensures that only authorized entities can access resources, protecting sensitive data and maintaining system integrity.

Why is Authentication necessary for DRIVR?

Authentication is crucial in DRIVR for:

1. Security: Protects accounts, data, and resources from unauthorized access.
2. User Trust: Builds confidence by safeguarding user data.
3. Compliance: Ensures adherence to data protection regulations.
4. Integrity: Verifies users and devices, reducing malicious risks.

Robust authentication ensures a secure and seamless user experience.

Prerequisites

Before diving into the authentication guide, make sure you’ve signed up and have created a Domain (your personalized DRIVR environment) through the DRIVR Customer Portal.

Here’s what you need to do:

1. Sign Up: Create an account by providing your email address, username, and password.
2. Create a Domain: Once signed up, set up your Domain, which acts as your unique identifier in the DRIVR API ecosystem.

Your Domain is essential for managing API resources, configuring authentication settings, and accessing the tools needed to implement authentication methods. Completing these steps ensures you’re ready to follow the instructions in this guide.

Types of Authentication Methods in DRIVR

This documentation provides comprehensive guidance on the various authentication methods supported by DRIVR. It covers the core concepts of API authentication and offers step-by-step instructions for setting up and configuring authentication across different scenarios.

1. Certificate-Based Authentication:
   A highly secure method that leverages digital certificates to verify the identity of entities, such as devices or applications, accessing the DRIVR MQTT API. Each entity is issued a unique digital certificate containing a public key and identifying information, which is validated against a trusted certificate authority (CA).

2. OAuth (Open Authorization):
   OAuth is a widely adopted industry-standard protocol designed for secure delegated access to APIs on behalf of a user. It enables third-party applications to interact with API resources without directly exposing the user's credentials.

   Key components of OAuth include:

   • Domain Authentication Methods: Ensures secure identification of the user's domain.
   • Application Consumers: Represents the third-party application requesting access.
   • GraphQL and REST APIs: Provides flexible interfaces for accessing and managing resources.

3. Token-Based Authentication:
   This method uses secure tokens to verify the identity of the requester. Tokens are generated and associated with a user or application, ensuring that only authorized entities can access the APIs.
4. OpenID (OIDC):
   DRIVR supports OpenID Connect (OIDC) for federated authentication, allowing users to securely log in using credentials from trusted providers like Google or Microsoft. OIDC builds on OAuth 2.0 by introducing an ID token (JWT) that carries user identity information, enabling seamless and secure sessions.
5. Local API Tokens:
   For specific use cases, DRIVR generates local tokens that authenticate users or systems within a limited scope or timeframe.These tokens are for on device local API authentication only. They can not be used for our GraphQL/REST/MQTT APIs but with an API a device might have locally.

By the end of this guide, you will gain a comprehensive understanding of the authentication methods available within DRIVR's APIs and be prepared to select the best approach for your specific needs.

If you have any questions or require further support, don’t hesitate to reach out to us at support@drivr.cloud.