31,003
edits
Authentication, SSO and SSL: Difference between revisions
m
→Description of available authentication modes
m (→googleoauth) Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 22: | Line 22: | ||
=Description of available authentication modes= | =Description of available authentication modes= | ||
==dolibarr== | ==Mode dolibarr== | ||
With this method, the login and pass you entered on login page will be compared to the login and the hashed password saved into the Dolibarr database (Table llx_user). | With this method, the login and pass you entered on login page will be compared to the login and the hashed password saved into the Dolibarr database (Table llx_user). | ||
==http== | ==Mode http== | ||
You can set the authentication mode to "http" if your Dolibarr web application is protected by an Apache http basic authentication form. The login/pass are stored into the file used by the HTTP Basic system to store passwords (it is often a file called '''.htpasswd''' if you used the '''mod_auth_basic''' + '''mod_authn_file''' plugin of Apache). | You can set the authentication mode to "http" if your Dolibarr web application is protected by an Apache http basic authentication form. The login/pass are stored into the file used by the HTTP Basic system to store passwords (it is often a file called '''.htpasswd''' if you used the '''mod_auth_basic''' + '''mod_authn_file''' plugin of Apache). | ||
| Line 34: | Line 34: | ||
Note that the user must also exists as a existing user into the Dolibarr user database. Also the date of validity of this user must be valid. | Note that the user must also exists as a existing user into the Dolibarr user database. Also the date of validity of this user must be valid. | ||
==ldap== | ==Mode ldap== | ||
If you set the authentication mode to LDAP, the test of the validity of your login and password are done using a LDAP database. | If you set the authentication mode to LDAP, the test of the validity of your login and password are done using a LDAP database. | ||
| Line 44: | Line 44: | ||
<br /> | <br /> | ||
==forceuser== | ==Mode forceuser== | ||
When this method is used, there is no need to enter a login or password. No login page is show. The user will be automatically set to the one defined into the variable '''$dolibarr_auto_user''' saved into '''htdocs/conf/conf.php''' | When this method is used, there is no need to enter a login or password. No login page is show. The user will be automatically set to the one defined into the variable '''$dolibarr_auto_user''' saved into '''htdocs/conf/conf.php''' | ||
| Line 52: | Line 52: | ||
<br /> | <br /> | ||
==googleoauth== | ==Mode googleoauth== | ||
This code is to use the Google OAuth 2 authentication. It is available with version 18+. | This code is to use the Google OAuth 2 authentication. It is available with version 18+. | ||
| Line 63: | Line 63: | ||
Now try to login. You must enter your Google account and you will be able to login without password if and only if a user exists into the Dolibarr database with the same email address than the one used to login to Google. | Now try to login. You must enter your Google account and you will be able to login without password if and only if a user exists into the Dolibarr database with the same email address than the one used to login to Google. | ||
==openid== | ==Mode openid== | ||
This method is an old method for using openID. | This method is an old method for using openID. | ||
==openid_connect== | ==Mode openid_connect== | ||
===OpenID Connect using the native method=== | ===OpenID Connect using the native method=== | ||