<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>UnicodePwd on Evan Hoffman</title><link>https://evan.wtf/tags/unicodepwd/</link><description>Recent content in UnicodePwd on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 13 Jan 2010 13:51:43 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/unicodepwd/index.xml" rel="self" type="application/rss+xml"/><item><title>Victory! Change Active Directory Password via LDAP through browser</title><link>https://evan.wtf/2010/01/13/victory-change-active-directory-password-via-ldap-through-browser/</link><pubDate>Wed, 13 Jan 2010 13:51:43 +0000</pubDate><guid>https://evan.wtf/2010/01/13/victory-change-active-directory-password-via-ldap-through-browser/</guid><description>&lt;p&gt;I had to give up on PHP and go to Perl, but it turned out not to be so bad. Users can now change their Active Directory passwords via a self-service web page that doesn&amp;rsquo;t require admin credentials. The Perl code is below. Authentication to the script is done via .htaccess LDAP authentication, so the REMOTE_USER env variable is assumed to contain the user&amp;rsquo;s username (sAMAccountName) by the time this script is called. There is a simple check for $ENV{HTTPS} to ensure the script is called via SSL, and AD requires password changes to be done via ldaps, so the whole thing &lt;em&gt;should&lt;/em&gt; be encrypted end to end.&lt;/p&gt;</description></item><item><title>LDAP-Active Directory authentication, Part 3</title><link>https://evan.wtf/2010/01/08/ldap-active-directory-authentication-part-3/</link><pubDate>Fri, 08 Jan 2010 19:12:34 +0000</pubDate><guid>https://evan.wtf/2010/01/08/ldap-active-directory-authentication-part-3/</guid><description>&lt;p&gt;So I got everything working with .htaccess and AD/LDAP authentication. Just add LDAPVerifyServerCert Off to the httpd config to let Apache authenticate against an AD server with a self-signed certificate (without dealing with the annoyance of putting the cert on each Apache server).&lt;/p&gt;&#10;&lt;p&gt;With that piece of the puzzle largely solved, I moved on to another: how will users change their passwords (which are all stored in Active Directory)? For users running Windows this is pretty trivial &amp;ndash; they can do it right in Windows when they&amp;rsquo;re logged into the domain. But what about Linux users? I figured the easiest thing to do would be to make a web form to do this. The user would login (with the http/LDAP auth I previously setup) and the form would ask for their password (twice) and update it in Active Directory. Sounds pretty simple to me. I think if this were OpenLDAP it probably would be, but being AD, it&amp;rsquo;s not.&lt;/p&gt;</description></item></channel></rss>