Zen

Translation

English type: Title ##
More to come
13/120 · 12

Sign in to save the translation.

English Arabic Actions
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.
 
You will now have to fill some settings.
 
This is the button label in the following screenshot:
 
For now, it is not possible to localize this label.
 
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`.
 
Note: if your provider use the standard `/.well-known/openid-configuration` path, you can omit it. For example `https://accounts.google.com` will work.
 
Your application Client ID.
 
You application Client secret.
 
Google, Facebook, ...
 
In addition to that, you can also configure one or several "standard" Open ID Connect provider (Google, Facebook, ...).
 
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.
 
Note: if you are connected to your Peertube account, the button will never show. So use a private browser window to test.
 
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.
 
More to come
المزيد لاحقا…
Other authentication methods will be implemented in the future.
 
Plugin Peertube Livechat administration
 
Admin documentation
مستندات الإدارة
Advanced firewall rules for the Prosody server
 
Prosody mod_firewall
 
You can enable [mod_firewall](https://modules.prosody.im/mod_firewall) on your Prosody server.
 
Doing so, Peertube admins will be able to define advanced firewall rules.
 
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.
 
Edit rules
تعديل القواعد
First, you must enable the feature in the [plugin settings](/peertube-plugin-livechat/documentation/admin/settings).
 
Just bellow the settings, you will find a "Configure mod_firewall" button. This button will open a configuration page.
 
![Screenshot of the "{{% livechat_label prosody_firewall_configuration %}}" form.](/peertube-plugin-livechat/images/mod_firewall.png?classes=shadow,border&height=400px "{{% livechat_label prosody_firewall_configuration %}}")
 
Here you can add several configuration files.
 
You can enable/disable each files.
 
Files will be loaded in the alphabetical order. You can use a number as prefix to easily choose the order.
 

Loading…

User avatar ButterflyOfFire

Translation added
More to come
المزيد لاحقا…
a month ago
User avatar None

String added in the repository
More to come
 
5 months ago
Browse all string changes

Things to check

Mismatched ellipsis

Source and translation do not both end with an ellipsis

Reset

Glossary

English Arabic
No related strings found in the glossary.

String information

Source string description
type: Title ##
Flags
no-wrap
Source string location
build/documentation/pot_in/documentation/admin/external_auth.md
String age
5 months ago
Last updated
3 weeks ago
Source string age
5 months ago
Translation file
support/documentation/po/livechat.ar.po, string 329