Stirling-Tools / Stirling-PDF

At the moment its hardcoded for one of the following providers;

Keycloak
Google
GitHub

Could we have a provider called "custom" or something you can brand yourself. There are lots of different providers out there and thinking a generic provider (or client looking at the config) reference will help reduce the amount of coding work in the future setting up each provider within the code. Unless truly needed due to some unique configuration settings.

I am using Authelia and as a workaround I am using the provider/client "keycloak" which works but the UI is all branded as Keycloak as the SSO provider which could confuse users

Hi, we have it see:

Stirling-PDF/src/main/resources/settings.yml.template

Lines 13 to 21 in 316b4e4

    
           #  oauth2: 
        
           #    enabled: false # set to 'true' to enable login (Note: enableLogin must also be 'true' for this to work) 
        
           #    issuer: "" # set to any provider that supports OpenID Connect Discovery (/.well-known/openid-configuration) end-point 
        
           #    clientId: "" # Client ID from your provider 
        
           #    clientSecret: "" # Client Secret from your provider 
        
           #    autoCreateUser: false # set to 'true' to allow auto-creation of non-existing users 
        
           #    useAsUsername: "email" # Default is 'email'; custom fields can be used as the username 
        
           #    scopes: "openid, profile, email" # Specify the scopes for which the application will request permissions 
        
           #    provider: "google" # Set this to your OAuth provider's name, e.g., 'google' or 'keycloak'

New providers are only encoded if they have a different behavior that others do not have, e.g. the logout with keycloak

	# oauth2:
	# enabled: false # set to 'true' to enable login (Note: enableLogin must also be 'true' for this to work)
	# issuer: "" # set to any provider that supports OpenID Connect Discovery (/.well-known/openid-configuration) end-point
	# clientId: "" # Client ID from your provider
	# clientSecret: "" # Client Secret from your provider
	# autoCreateUser: false # set to 'true' to allow auto-creation of non-existing users
	# useAsUsername: "email" # Default is 'email'; custom fields can be used as the username
	# scopes: "openid, profile, email" # Specify the scopes for which the application will request permissions
	# provider: "google" # Set this to your OAuth provider's name, e.g., 'google' or 'keycloak'

[Feature Request] Have a OAUTH Provider called "custom" or brandable