<html><head><style type='text/css'>p { margin: 0; }</style><style type='text/css'>body { font-family: 'Times New Roman'; font-size: 12pt; color: #000000}</style></head><body>Mike,<br><br>I would certainly like to see this. <br><br>*wish mode*<br><br>If you could drag down group memberships as well and if they exist in RT, then add that user to those RT groups, I would love to see that as well as it would mean all the functionality for User creation could be setup via LDAP as well. MediaWiki does this and it works well (although far less complicated than RT I suspect).<br><br>Cheers,<br>David<br>----- Original Message -----<br>From: "Mike Peachey" <mike.peachey@jennic.com><br>To: "Kenneth Crocker" <KFCrocker@lbl.gov><br>Cc: "Pedro Lobo S. da Rocha" <pedrolobo.rocha@gmail.com>, "RT Users" <rt-users@lists.bestpractical.com><br>Sent: Saturday, 12 April, 2008 9:51:45 PM GMT +10:00 Brisbane<br>Subject: Re: [rt-users] SOLVED? LDAP_INVALID_CREDENTIALS error with 'ExternalAuth' extension<br><br>I have a thought. I don't know whether I will need to override the <br>AutoCreate method or if I can do it all just by passing params from the <br>autohandler auth callback, but it seems reasonable that I should be able <br>to easily allow LDAP users to be autocreated as Privileged, while <br>leaving the default AutoCreation at unprivileged.<br><br>This way, by way of a configuration setting, that is individual to each <br>ExternalAuth configuration group (LDAP/DBI etc) you could specify <br>whether to autocreate as privileged or unprivileged, and RT would still <br>retain it's own default setting for *other* users..<br><br>Do you think this is something you'd want built into the extension?<br><br>Opinions welcome.<br>--<br>Kind Regards,<br><br>___________________________________________________<br><br>Mike Peachey, IT<br>Tel: +44 (0) 114 281 2655<br>Fax: +44 (0) 114 281 2951<br>Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK<br>http://www.jennic.com<br>Confidential<br><br></body></html>