Immich currently supports OpenID Connect (OIDC) authentication, but its initial setup process requires manual configuration, preventing seamless integration.
The core of the issue lies within the authentication module's handling of redirect URIs. It's presently restricted to accepting only URIs with the server's domain name. This creates a problem for Immich's mobile application, which relies on a specific redirect URI: app.immich:///oauth-callback.
To resolve this, the authentication module needs to be updated to allow for alternative redirect URIs, such as those used by the mobile application, during the initial OIDC setup. This enhancement would streamline the setup process and improve compatibility with Immich's various client applications.
Immich currently supports OpenID Connect (OIDC) authentication, but its initial setup process requires manual configuration, preventing seamless integration.
The core of the issue lies within the authentication module's handling of redirect URIs. It's presently restricted to accepting only URIs with the server's domain name. This creates a problem for Immich's mobile application, which relies on a specific redirect URI:
app.immich:///oauth-callback.To resolve this, the authentication module needs to be updated to allow for alternative redirect URIs, such as those used by the mobile application, during the initial OIDC setup. This enhancement would streamline the setup process and improve compatibility with Immich's various client applications.