Removes temporary test endpoints and refactors the authorize endpoint.
Adds support for VIN notifications for a new vehicle by adding it to the dictionary.
The application now redirects to the Tesla authorization endpoint when the access token is missing.
This ensures the user is prompted to authorize the application.
Adds query parameters for latitude and longitude to the `/TestStartParking` endpoint, allowing to simulate different locations.
Adds logic to set the gear to "P" if the received value is null to cover edge cases.
Ensures asynchronous message processing by awaiting the result of ProcessMessage to prevent potential race conditions.
Ensures the RePair endpoint includes the VIN in the telemetry config request.
This guarantees that telemetry data is specifically requested for the provided VIN.
Updates the hardcoded access token used in the /RePair endpoint.
The previous token was likely outdated or invalid, preventing the endpoint from functioning correctly. This change ensures the endpoint can properly authenticate and access necessary resources.
Specifies that the logger and http client factory should be injected via dependency injection instead of directly from the request.
This allows for better testability and separation of concerns.
Implements fleet telemetry configuration by first removing the existing telemetry configuration and then posting a new configuration.
This configures telemetry data collection intervals and host information.
Adds logging for request/response from the API.
Adds an endpoint to retrieve fleet status information.
This endpoint uses a Tesla API proxy to fetch the fleet status
based on provided VINs. It handles authentication using a bearer
token and sends a POST request to the /api/1/vehicles/fleet_status
endpoint.
Also introduces new data models to properly serialize/deserialize the fleet status response.
Removes the redundant base address and header configurations from within the endpoint handler. This configuration should be handled elsewhere, avoiding unnecessary repetition.
Changes the application registration endpoints to use the ITeslaAuthenticatorService interface.
Updates the KeyPairing endpoint to redirect to the correct Tesla connector app.
Adds a new KeyPairing2 endpoint.
Reads telemetry configuration parameters such as hostname, port, and CA certificate from an external JSON file.
This decouples configuration from code, allowing for easier updates and management of telemetry settings.
Removes the explicit setting of the "Content-Type" header,
as HttpClient handles this automatically based on the content being sent.
This change simplifies the code and avoids potential conflicts
if the content type is already being set elsewhere.
Adds named HTTP client configuration with insecure settings to
communicate with the tesla_command_proxy, which uses a self-signed
certificate.
Changes the base address to use HTTPS.
Changes the redirect URI after successful authorization to a more specific endpoint, likely to integrate with a UI or service named "Tesla". This allows the application to properly handle the authorization response and proceed with the next steps.
Changes from `RedirectToRoute` to `LocalRedirect` for the
authorization endpoint to improve security and ensure the
redirect stays within the application's domain.
Adds an endpoint to interact with the Tesla API via a command proxy.
This includes fetching vehicle information and configuring telemetry settings. It introduces new models to represent the Tesla API responses and request structures.
Configures the Tesla OIDC endpoints using the base URL
to dynamically set authorization, token, JWKS URI, end
session, and user info endpoints. This eliminates the need
for a URL override function and centralizes the endpoint
configuration logic.
Configures the OpenID Connect (OIDC) authentication flow by
explicitly setting the authorization, token, JWKS, end session, and
user info endpoints.
This change removes the custom OIDC configuration manager and
directly sets the configuration within the OIDC options. This approach
simplifies the configuration and ensures that the application uses
the correct endpoints for authentication and authorization with the
third-party provider.
Updates the authentication configuration to utilize Fleet-Auth's third-party OIDC configuration.
This change streamlines the authentication process by directly pointing to the third-party metadata and adds the Fleet API audience to the token request, ensuring proper authorization for accessing Tesla's Fleet API. It also configures Tesla specific parameters.
Improves authentication by adding a signing key resolver and overriding the token endpoint.
This change ensures proper validation of Tesla's OIDC tokens by fetching the signing keys from the issuer's `certs` endpoint and caching them. It also configures the token endpoint required for Tesla authentication.
Disables issuer validation during token authentication.
The token validation parameters are adjusted to bypass
issuer validation, since the issuer is already validated via the `ValidIssuers` parameter.
Adds multiple valid issuers to the authentication configuration.
This ensures compatibility with different Tesla authentication endpoints,
including fleet and regional variations.
Adds detailed logging of request headers for debugging purposes.
Clears known networks and proxies in forwarded headers options.
This change improves the ability to diagnose issues related to
request handling and forwarding in different environments.
Ensures the application correctly handles forwarded headers
by explicitly setting the `ForwardedHeaders` option to `ForwardedHeaders.All`.
This allows the application to properly determine the client's
IP address and other request information when behind a proxy
or load balancer.
Adds ForwardedHeaders to handle reverse proxy scenarios.
Adds a debug endpoint to display the correct scheme and host
when running behind a reverse proxy, aiding in debugging
authentication issues.
Updates the callback path for authentication to a relative path.
This change removes the hardcoded domain from the callback URL,
making the application more flexible and easier to deploy in
different environments.
Removes a redundant host config in the docker file.
Adds HttpContextAccessor to the service collection. This
component is used to provide access to the current request context.
Implements authentication against the Tesla Fleet API using OpenID Connect.
Uses a custom OIDC configuration manager to override the token endpoint.
Configures authentication services and adds required scopes and parameters.
Adds endpoints for application registration and token retrieval during development.
Implements the /Authorize endpoint to redirect users to the Tesla
authentication page. This allows users to grant the application
permission to access their Tesla account data.
Updates the public key resource to be copied on build, ensuring
it is always available at runtime.
Adds logic to validate the application registration by comparing the
public key retrieved from the Tesla API with the public key stored
locally.
