{"id":544935,"date":"2010-04-27T03:00:00","date_gmt":"2010-04-27T07:00:00","guid":{"rendered":"tag:blogger.com,1999:blog-1652419620964346731.post-27261134227957925"},"modified":"2010-04-27T03:00:00","modified_gmt":"2010-04-27T07:00:00","slug":"how-to-make-osticket-1-6-0-authenticate-with-active-directory","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/544935","title":{"rendered":"How To Make osTicket 1.6.0 Authenticate with Active Directory"},"content":{"rendered":"

Back in September of last year I wrote up an article on how to get osTicket to authenticate with Active Directory<\/a>. That article was based on version 1.6 RC5. It actually worked very well for my company. Users could simply login to the staff panel with their domain\\username credentials.<\/p>\n

Well, we started getting weird database errors recently, so I thought it might be good to move away from the RC5 version, and move to the final release. Well, if you read the comments at the bottom of my previous article you will know that my customizations didn\u2019t carry over to the final release. That is ok though, because I found an even better and easier way to get osTicket to authenticate with AD. I got it working in about 2 minutes in Ubuntu Server 10.04.<\/p>\n

First you will need one little perquisite package, php5-ldap<\/strong>. Just run the following:<\/p>\n

\n

>sudo apt-get install php5-ldap<\/span><\/p>\n<\/blockquote>\n

Next you will want to manually create a user with a username that matches active directory. For instance is your AD username is jsmith<\/em> create a user in osTicket called jsmith and give it a temporary password of 123456 (Doesn’t matter because osTicket will look to AD right?)<\/p>\n

Once that is installed, edit include\/class.staff.php<\/strong>:<\/p>\n

\n

>sudo nano include\/class.staff.php<\/span><\/p>\n<\/blockquote>\n

Replace the following code:<\/p>\n

\n

\/*compares user password*\/
function check_passwd($password){
return (strlen($this->passwd) && strcmp($this->passwd, MD5($password))==0)?(TRUE):(FALSE);
}<\/span><\/p>\n<\/blockquote>\n

With:\"osticket\"<\/a> <\/p>\n

\n

\/*compares user password*\/
function check_passwd($password){
\/\/ Change made for LDAP Auth based on -> http:\/\/osticket.com\/forums\/showthread.php?t=3312
\/\/ Change this line to the FQDN of your domain controller
$ds=ldap_connect('mydc.mydomain.local'<\/strong><\/span>) or die(\"Couldn't connect to AD!\");
\/\/ Change this line to the name of your Active Directory domain
if ($ds) {
$domain=\"mydomain<\/span><\/strong>\";
$ldapbind = ldap_bind($ds);
if (!@ldap_bind( $ds, $domain.\"\\\\\".$this->username, $password) ) {
\/\/ Auth failed! lets try at osTicket database
return (strlen($this->passwd) && strcmp($this->passwd, MD5($password))==0)?(TRUE):(FALSE);
\/\/ return(FALSE);
}
else{
\/\/ Auth succeeded!
return(TRUE);
}
\/\/ End Changes
}<\/span><\/code><\/code><\/p>\n

}<\/span>
<\/code><\/code><\/p>\n<\/blockquote>\n

<\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n

After you do that change the items in red to match your environment then restart Apache:<\/code><\/code><\/p>\n

\n

>sudo \/etc\/init.d\/apache2 restart<\/span><\/code><\/code><\/p>\n<\/blockquote>\n

Bam! You now have Microsoft Active Directory authentication, and you don\u2019t have to specify a domain name at login either!<\/code><\/code><\/p>\n

If you are looking for additional functionality, check out the osTicket Forums, there are a lot of cool customizations I am sure you will find useful!<\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n<\/p>\n

Technorati Tags: osticket<\/a>,1.6<\/a>,active directory<\/a>,authentication<\/a>,how to<\/a><\/div>\n


\n\"Great<\/a><\/center><\/div>\n
\n<\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a>\n<\/div>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Back in September of last year I wrote up an article on how to get osTicket to authenticate with Active Directory. That article was based on version 1.6 RC5. It actually worked very well for my company. Users could simply login to the staff panel with their domain\\username credentials. Well, we started getting weird database […]<\/p>\n","protected":false},"author":1521,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-544935","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/544935","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/users\/1521"}],"replies":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/comments?post=544935"}],"version-history":[{"count":0,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/544935\/revisions"}],"wp:attachment":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/media?parent=544935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/categories?post=544935"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/tags?post=544935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}