Shawn,
Thanks for the fix.
I'll rework my configuration once the commit is merged, things in that
department are working ok at the moment and I'm still fighting other
small fires from the transition.
Much appreciate the update and fix though!
Kind regards
Bart
Shawn Moore
On 2016年5月24日 at 20:27:02, Bart Bunting (bart.bunt...@ursys.com.au) wrote:
> Hi there,
Hi Bart,
> I may be just missing something but this is failing miserably for me and
> I am not sure what the correct way to fix it is:
>
> Running rt 4.4.1 rc1 as of today.
I’m glad to hear it. :)
> When I
Hi Jim,
Sorry for not posting the relevant details. It is a totally new install
being built to replace our customized version of rt 3.6 :). Probably
time for an upgrade :).
Here are the configuration details that are to do with authentication.
As previously mentioned I think the error is
To clarify the previous question, if you were using
RT::Authen::ExternalAuth in a previous version of RT (pre-4.4) and have
it pulled in as a Plugin, you need to remove it because it is now in
core. It's not clear to me if your RT_SiteConfig.pm is from an earlier
RT version. If so, you will
Peter,
Not sure, but this is a new install using rt 4.4.
Kind regards
Peter Viskup writes:
> Couldn't this be related to RT::Authen::ExternalAuth migration to RT
> core since 4.4 version?
>
> https://docs.bestpractical.com/rt/4.4.0/UPGRADING-4.4.html
>
> --
> Peter
>
>
Couldn't this be related to RT::Authen::ExternalAuth migration to RT
core since 4.4 version?
https://docs.bestpractical.com/rt/4.4.0/UPGRADING-4.4.html
--
Peter
On Wed, May 25, 2016 at 2:26 AM, Bart Bunting wrote:
>
> Hi there,
>
> I may be just missing something
Hi there,
I may be just missing something but this is failing miserably for me and
I am not sure what the correct way to fix it is:
Running rt 4.4.1 rc1 as of today.
The situation is I have external authentication working fine using both
RT::Authen::ExternalAuth and RT::LDAPImport.
I use