<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>Re: [rt-users] LDAP integration question</title>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
body {
margin: 5px 5px 5px 5px;
background-color: #ffffff;
}
/* ========== Text Styles ========== */
hr { color: #000000}
span.rvts1 /* Heading */
{
font-size: 10pt;
font-family: 'Arial';
font-weight: bold;
color: #0000ff;
}
span.rvts2 /* Subheading */
{
font-size: 10pt;
font-family: 'Arial';
font-weight: bold;
color: #000080;
}
span.rvts3 /* Keywords */
{
font-size: 10pt;
font-family: 'Arial';
font-style: italic;
color: #800000;
}
a.rvts4, span.rvts4 /* Jump 1 */
{
font-size: 10pt;
font-family: 'Arial';
color: #008000;
text-decoration: underline;
}
a.rvts5, span.rvts5 /* Jump 2 */
{
font-size: 10pt;
font-family: 'Arial';
color: #008000;
text-decoration: underline;
}
span.rvts6
{
font-size: 8pt;
font-family: 'arial';
font-style: italic;
}
a.rvts7, span.rvts7
{
font-size: 8pt;
font-family: 'arial';
color: #0000ff;
text-decoration: underline;
}
span.rvts8
{
font-size: 8pt;
font-family: 'arial';
font-style: italic;
}
a.rvts9, span.rvts9
{
color: #0000ff;
text-decoration: underline;
}
/* ========== Para Styles ========== */
p,ul,ol /* Paragraph Style */
{
text-align: left;
text-indent: 0px;
padding: 0px 0px 0px 0px;
margin: 0px 0px 0px 0px;
}
.rvps1 /* Centered */
{
text-align: center;
}
--></style>
</head>
<body>
<p>You'll want to look into the ExternalAuth extension for RT (<a class=rvts9 href="http://wiki.bestpractical.com/view/ExternalAuth">http://wiki.bestpractical.com/view/ExternalAuth</a>). It supports login via LDAP.</p>
<p><br></p>
<p>- D</p>
<p><span class=rvts6>-- </span></p>
<p><span class=rvts6>Daniel Farst</span></p>
<p><span class=rvts6>IT Support Coordinator</span></p>
<p><span class=rvts6>College of Arts and Sciences</span></p>
<p><span class=rvts6>Case Western Reserve University</span></p>
<p><br></p>
<p><span class=rvts6>----------------------------------</span></p>
<p><span class=rvts6>Thursday, March 19, 2009, 4:15:45 PM, you wrote:</span></p>
<p><span class=rvts6>----------------------------------</span></p>
<p><span class=rvts8>> Greetings all,</span></p>
<p><span class=rvts8>> I'm only in the early analysis stage of trying to figure</span></p>
<p><span class=rvts8>> out if RT is a good fit for us. We currently use Trac for our ticketing</span></p>
<p><span class=rvts8>> system, which is workable, but not universally liked (being more of</span></p>
<p><span class=rvts8>> an appropriate solution for an ongoing open-source project </span></p>
<p><span class=rvts8>> than it is for a small college IT helpdesk). Anyhow, I have a test</span></p>
<p><span class=rvts8>> instance of RT+AssetTracker up and running on an old </span></p>
<p><span class=rvts8>> underpowered VM, but I'm definitely only scratching the surface (I</span></p>
<p><span class=rvts8>> have the _RT Essentials_ book but I haven't yet read it all the </span></p>
<p><span class=rvts8>> way through). My question is about how to leverage our LDAP</span></p>
<p><span class=rvts8>> directory in order to allow end-users to create tickets. We have a </span></p>
<p><span class=rvts8>> small enough staff that creating local RT users for our admin</span></p>
<p><span class=rvts8>> personnel is not a problem (I have no requirement to also sync this </span></p>
<p><span class=rvts8>> information from LDAP as it's easily manageable as an independent</span></p>
<p><span class=rvts8>> data silo (living within the RT database backend I presume)). </span></p>
<p><span class=rvts8>> But what is the canonical solution for allowing our users to login</span></p>
<p><span class=rvts8>> to the web interface (using their existing usernames/passwords </span></p>
<p><span class=rvts8>> which we already have set in LDAP (for their email accounts among</span></p>
<p><span class=rvts8>> other uses))? Do I want to be leveraging the HTTP-auth stuff </span></p>
<p><span class=rvts8>> from apache (I believe this is how we solve this issue with Trac</span></p>
<p><span class=rvts8>> currently), or is there a way to have RT directly query a </span></p>
<p><span class=rvts8>> specific PAM layer that's been configured correctly (to back</span></p>
<p><span class=rvts8>> against our LDAP) on the RT server? Or maybe there's a different way</span></p>
<p><span class=rvts8>> to accomplish what I want. I made it into the beginning of the</span></p>
<p><span class=rvts8>> chapter on scrips last night, so I have no doubt that (given more </span></p>
<p><span class=rvts8>> perl coding chops than I currently possess) there are definitely</span></p>
<p><span class=rvts8>> enough tools available to solve this problem, but it seemed worth </span></p>
<p><span class=rvts8>> asking for direction (as I can't imagine I'm the first person to want to do this).</span></p>
<p><br></p>
<p><span class=rvts8>> thanks so much in advance for any information,</span></p>
<p><span class=rvts8>> ~c</span></p>
<p><span class=rvts8>> _______________________________________________</span></p>
<p><span class=rvts8>> </span><a class=rvts7 href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a></p>
<p><br></p>
<p><span class=rvts8>> Community help: </span><a class=rvts7 href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</a></p>
<p><span class=rvts8>> Commercial support: </span><a class=rvts7 href="mailto:sales@bestpractical.com">sales@bestpractical.com</a></p>
<p><br></p>
<p><br></p>
<p><span class=rvts8>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. </span></p>
<p><span class=rvts8>> Buy a copy at </span><a class=rvts7 href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</a></p>
</body></html>