Kevin, I guess that when I read things, I read them differently. From what I read about ExternalAuth, I assumed it did the authorizing but didn't see where it *defaulted back* to RT (checking the USERS Table) when an ExternalAuth failed. My mistake, again. I did figure that if ExternalAuth allowed a non-LDAP to be added (per setting) that the regular AutoCreate,Privileged, 0/1 setting would determine whether they were added as privileged or not, but I didn't realize that if the Auth didn't Pass LDAP, RT would look at the Users DataBase for the User. I just didn't see it that way when I read the documentation. No one's fault but my own. Sorry.
Kenn LBNL On Thu, Jan 13, 2011 at 10:42 AM, Kevin Falcone <[email protected]>wrote: > On Thu, Jan 13, 2011 at 10:37:03AM -0800, Kenneth Crocker wrote: > > I do have a question as to why all that explanation on My_Oracle and > such in the ExternalAuth > > notes if we should use such settings? > > Because you can validate against some other app's database? > > What gave you the idea that you needed to configure > RT-Authen-ExternalAuth to talk to RT's internal Users table? > Documentation implying that needs to be fixed > > -kevin >
