Warning, if you are using this plugin in slave mode with Drupal, Joomla or Wordpress, and encounter problems for connecting to Pydio with the REST clients (iPhone/iPad, webDav), you have to upgrade the plugin. More info can be found here
Generic plugin used for integration with various CMS. In master mode, when you login, Pydio will silently call a predefined URL to also log you on the external application. In slave mode, the plugin is not straightforward to implement, you should check the wordpress and joomla implementation for more examples. Basically, in slave mode, it works as follow :

- Install Pydio with a " standard " authentication plugin, and update your " admin " user with your own password.
- Then switch to this auth.remote plugin in the server/conf/conf.php file.
- In the config, set a secret key (can be anything, not necessary your admin password, beware of " anti-slashing " $ symbol).
- It's ready to use on the Pydio part
- In your CMS, create an authentication mechanism (generally there is also a plugin system) that can be configured with the secret key.
- This mechanism must, at login time, include the plugins/auth.remote/glueCode.php file, the secret key being set as GLOBAL before the inclusion, as well as the $plugInAction variable, and other variable depending on the action (login, logout, addUser, etc).. See the glueCode file to check the implemented actions.
- This way, the glueCode file switches dynamically the session to an Pydio session, logs in a user, then give back the hand to the CMS.
- Once logged in your CMS, you should be able to access Pydio logged in as the same user.

In order to make the mobile clients working with this auth.remote plugin, you have to carefully configure the MASTER_XX options. Please see a brief description below, but above all read the dedicated description in the documentation on the website configuring-auth-remote-for-the-mobile-clients

- MASTER_AUTH_FUNCTION will be « drupal_remote_auth« , « joomla_remote_auth » or « wordpress_remote_auth » depending on the bridge you are using. See below on how to add your own custom function if your CMS is different.
- MASTER_HOST can be detected automatically, but otherwise set to the host of your cms installation (so it can be 192.168.0.25, or localhost, or www.mycms.com). Most generally for shared hosts it will be your real domain name, not a local adress. Warning, no trailing slahs.
- MASTER_URI will be the path on your host to your CMS, beginning with a slash. Can be something like « /wordpress » or « /wordpress/ » … The combination of MASTER_HOST and MASTER_URI should lead to the page containing the login form.
- MASTER_AUTH_FORM_ID : (useless for WP) The HTML identifier of the login form as it appear in the login page. You can use F12 (developer tools) in most modern browser, to inspect the HTML and find the corresponding <form> tag and it’s id attribute : <form id= »login-form »> bla …. </form>