Would be nice to have PAM auth builtin or capabilities. <br><br><div><span class="gmail_quote">On 5/1/07, <b class="gmail_sendername">Philip Kime</b> <<a href="mailto:pkime@shopzilla.com">pkime@shopzilla.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One thing I saw mentioned was Mandatory field support - we implemented a<br>pretty robust Mandatory field system in RT here with a separate checkbox
<br>so that validation and Mandatory are separate. Also pushed all the code<br>into the core API so it works via REST, email and GUI. This has been<br>submitted as patches against 3.6.3.<br><br>Another thing is the ability to display (and sort by) the RealName of
<br>users everywhere instead of the Name field. This is crucial in (silly)<br>places where the policy is to have completely numeric usernames (like<br>AD/LDAP authentication where corporate policy is employee IDs as<br>usernames ...). RT is really crippled if you can't tell easily by
<br>looking, who did what. I have patches to put in two flags to decide<br>which to display, against 3.6.3. Jesse mentioned that this might already<br>be in 3.7 but I installed 3.7.1 and there doesn't seem to be anything in
<br>there like this.<br><br><br>PK<br>_______________________________________________<br><a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
</a><br><br>Community help: <a href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</a><br>Commercial support: <a href="mailto:sales@bestpractical.com">sales@bestpractical.com</a><br><br><br>Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
<br>Buy a copy at <a href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</a><br></blockquote></div><br><br clear="all"><br>-- <br>Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu">
pgp.mit.edu</a><br><br><br>