To enable this feature, first you have to create a client on your provider side (check the related documentation for enabling OpenID Connect).Then go to the [pluginsettings](/peertube-plugin-livechat/documentation/admin/settings), and enable "{{% livechat_label external_auth_custom_oidc_label %}}".
Note: if you want to restrict allowed redirection urls on the provider side (best security practice), the plugin will show you the url to allow.Just copy it in your OpenID Connect application configuration.
Your OpenID Connect provider must implement the [discovery URL](https://openid.net/specs/openid-connect-discovery-1_0.html).Just set here the discovery url, that should be something like `https://example.com/.well-known/openid-configuration`.
For these providers, discovery url and button label are preset.You just have to create an OAuth2 application on the provider side, and configure Client ID and Client Secret.
If you think of a standard provider that is not available, you can ask for implementation by [opening a new issue](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues).
If the button does not appear for end users, there might be a configuration issue.You can try the [diagnostic tool](/peertube-plugin-livechat/documentation/installation/troubleshooting/) to get more information.
If the button is displayed but is not working, check your Peertube logs.It could be because the remote service does not use standard scopes or attribute names.
