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.
These rules could be used to run arbitrary code on the server.If you are a hosting provider, and you don't want to allow Peertube admins to write such rules, you can disable the online editing by creating a `disable_mod_firewall_editing` file in the plugin directory (`plugins/data/peertube-plugin-livechat/disable_mod_firewall_editing`).This is opt-out, as Peertube admins can already run arbitrary code just by installing any plugin.You can still use mod_firewall by editing files directly on the server.
