Thursday, September 25, 2008
Authentication: standard, http, LDAP
Teamwork currently (3.2.8) supports a built-in, we’ll call it “standard”, authentication (notice that Teamwork works fine also under https) , which is the usual login, and authentication provided by the container, we’ll call it “http authentication”. This allows both single-sign-on support and also LDAP authentication through say the Tomcat container, as detailed in the forum.
We are empowering authentication with a third modality, by having Teamwork contact directly the LDAP server, and also importing and updating users from LDAP via a scheduled job if needed. All this includes Active Directory; in this way, your LDAP will be the source of users and authentication. This third modality we’ll call it “LDAP”. It will make integration very easy, feasible completely just through the web interface. :-)
If users will require it, it will be quite easy to integrate also OpenId authentication.
UPDATE: Teamwork 3.2.9 includes direct LDAP import and authentication: see
We are empowering authentication with a third modality, by having Teamwork contact directly the LDAP server, and also importing and updating users from LDAP via a scheduled job if needed. All this includes Active Directory; in this way, your LDAP will be the source of users and authentication. This third modality we’ll call it “LDAP”. It will make integration very easy, feasible completely just through the web interface. :-)
If users will require it, it will be quite easy to integrate also OpenId authentication.
UPDATE: Teamwork 3.2.9 includes direct LDAP import and authentication: see
Labels: authentication, ldap, TeamworkTalk