SSO/HTTP
From Authentication Tools for Joomla! (JAuthTools)
(Difference between revisions)
(New page: HTTP Authentication utilises server provided authentication mechanisms to identify and authorize the users request. For Apache, numerous solutions do exist, a small selection below: * Bas...) |
|||
| Line 3: | Line 3: | ||
For Apache, numerous solutions do exist, a small selection below: | For Apache, numerous solutions do exist, a small selection below: | ||
* Basic | * Basic | ||
| - | * Kerberos | + | * [[Kerberos]] |
| - | * LDAP (e.g. user lookup) | + | * [[LDAP]] (e.g. user lookup) |
* DBD (e.g. MySQL, Postgres, Oracle, etc) | * DBD (e.g. MySQL, Postgres, Oracle, etc) | ||
For IIS, there are limited options: | For IIS, there are limited options: | ||
| - | * Basic (NTLM) | + | * Basic ([[NTLM]]) |
| - | * Kerberos (Negotiate) | + | * [[Kerberos]] (Negotiate) |
For either major system, further user details rely on parent schemes (e.g. LDAP provided by AD/eDirectory; MySQL DB with user information) provided by [[Users Sources]] to autocreate and manage users if necessary. | For either major system, further user details rely on parent schemes (e.g. LDAP provided by AD/eDirectory; MySQL DB with user information) provided by [[Users Sources]] to autocreate and manage users if necessary. | ||
| - | [[Category:SSO]] [[Category:Kerberos]] [[Category:MSAD]] | + | [[Category:SSO]] [[Category:LDAP]] [[Category:Kerberos]] [[Category:MSAD]] |
Revision as of 01:11, 20 April 2007
HTTP Authentication utilises server provided authentication mechanisms to identify and authorize the users request.
For Apache, numerous solutions do exist, a small selection below:
For IIS, there are limited options:
For either major system, further user details rely on parent schemes (e.g. LDAP provided by AD/eDirectory; MySQL DB with user information) provided by Users Sources to autocreate and manage users if necessary.
