Mike Peachey wrote:
> John McCoy wrote:
>> Good points Mike, I did not think about the fact that future users can
>> still get added as [EMAIL PROTECTED] if they first are just a requester, this
>> would mean I either need a constant process to "fix" these or as you
>> suggest:
>>
>>> Since Externa
John McCoy wrote:
> Good points Mike, I did not think about the fact that future users can
> still get added as [EMAIL PROTECTED] if they first are just a requester, this
> would mean I either need a constant process to "fix" these or as you
> suggest:
>
>> Since ExternalAuth has been refactored,
Good points Mike, I did not think about the fact that future users can
still get added as [EMAIL PROTECTED] if they first are just a requester, this
would mean I either need a constant process to "fix" these or as you
suggest:
Since ExternalAuth has been refactored, I could add an Overlay to
John McCoy wrote:
> I do have an additional issue now that I have had a few more testers try
> this:
> Most of our non-privileged users do already exist in RT as they have
> been auto added when the were added as requesters on a ticket, this has
> created their accounts as such:
>
> Username: [EMA
I do have an additional issue now that I have had a few more testers try
this:
Most of our non-privileged users do already exist in RT as they have
been auto added when the were added as requesters on a ticket, this has
created their accounts as such:
Username: [EMAIL PROTECTED]
Email: [EMA
John McCoy wrote:
> Mike thank you very much for working so hard on this issue.
> I am happy to report that the new version does now work for SelfService
> (for me)
>
> Just an FYI for others stuck authenticating against Novell eDir and
> using the lame non-password ldap_proxy accounts I had to ma
Mike thank you very much for working so hard on this issue.
I am happy to report that the new version does now work for SelfService
(for me)
Just an FYI for others stuck authenticating against Novell eDir and
using the lame non-password ldap_proxy accounts I had to make the
changes you were thi
database is empty. this is a fresh install on new server.
On Fri, Nov 7, 2008 at 2:19 AM, Mike Peachey <[EMAIL PROTECTED]>wrote:
> Aaron Zuercher wrote:
>
>> I'm still getting the same error:
>> Can't call method "SetDisabled" on an undefined value at
>> /opt/rt3/bin/../lib/RT/User_Overlay.pm li
Mike Peachey wrote:
> Aaron Zuercher wrote:
>> I'm still getting the same error:
>> Can't call method "SetDisabled" on an undefined value at
>> /opt/rt3/bin/../lib/RT/User_Overlay.pm line 1087.
>>
>> I installed over the top and recieved that error. so then I remove the
>> RT_AUTH dir from the p
Aaron Zuercher wrote:
> I'm still getting the same error:
> Can't call method "SetDisabled" on an undefined value at
> /opt/rt3/bin/../lib/RT/User_Overlay.pm line 1087.
>
> I installed over the top and recieved that error. so then I remove the
> RT_AUTH dir from the plugins folder and reinstall
I'm still getting the same error:
Can't call method "SetDisabled" on an undefined value at
/opt/rt3/bin/../lib/RT/User_Overlay.pm line 1087.
I installed over the top and recieved that error. so then I remove the
RT_AUTH dir from the plugins folder and reinstalled again. Same error.
Here is what
Aaron Zuercher wrote:
> wedding vegetables? :D
Yes. :)
>
> Mike,
> I'll test it ASAP, can I install over top of the old version or do I
> need to remove it? what is the recommended uninstall method?
>
Over the top is fine. User_Vendor.pm is still there, but has been
reduced to almost nothi
wedding vegetables? :D
Mike,
I'll test it ASAP, can I install over top of the old version or do I need to
remove it? what is the recommended uninstall method?
Aaron
On Thu, Nov 6, 2008 at 3:21 PM, Mike Peachey <[EMAIL PROTECTED]>wrote:
> To all you loving testers out there, I've been worki
To all you loving testers out there, I've been working my wedding
vegetables off trying to get a new completely refactored (and, more
importantly, working) version of RT::Authen::ExternalAuth out to you and
the first beta is now complete and attached to this e-mail.
It's also available from the SV
14 matches
Mail list logo
