ExternalAuth 'environment' type

RT Users
1

What happened to the ExternalAuth ‘environment’ type of authentication?

Took me a while to work out it appears to have dissappeared between
0.08 and 0.09.

I’ve cut’n’pasted the relevant 10 lines or so back into 0.09 on my RT
4.0.1 install and I’m off again.

Does anyone know the rationale for it’s removal? maybe I’ve done a bad thing?

Thanks,
Dave

2

What happened to the ExternalAuth ‘environment’ type of authentication?

Took me a while to work out it appears to have dissappeared between
0.08 and 0.09.

I’ve cut’n’pasted the relevant 10 lines or so back into 0.09 on my RT
4.0.1 install and I’m off again.

Does anyone know the rationale for it’s removal? maybe I’ve done a bad thing?

Running

git diff 0.08…0.09 | grep -i environment

in the rt-authen-externalauth git repo doesn’t find me any results.
Did you perhaps have a local mod?

If you’re referring to REMOTE_USER that’s something that RT handles
without an extension.

-kevin

3

Running

git diff 0.08…0.09 | grep -i environment

in the rt-authen-externalauth git repo doesn’t find me any results.
Did you perhaps have a local mod?

If you’re referring to REMOTE_USER that’s something that RT handles
without an extension.

-kevin

Wow, OK. Apparently I need to work on my documentation a bit more.

I’ve done this:

root@arty [PROD] /apps/rt/local/# diff
/apps/build/RT-Authen-ExternalAuth-0.09/lib/RT/Authen/ExternalAuth.pm
plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm
77a78,90

    #############################################################
    ##################### Environment Check #####################
    #############################################################
    if ($config->{'type'} eq 'environment') {
        # Check for the appropriate environment variable and
        # trust it
        if (defined($config->{'name'})) {
            $RT::Logger->debug( "Retreiving environment variable ",$config->{'name'} );
            $username = $ENV{$config->{'name'}};
            $RT::Logger->debug( "username retrieved is \"$username\"" );
        }
    }

It adds configurable element for an environment variable that contains
a username to be trusted. From memory my plans were to use webauth
eventually via the apache module/plugin.

The only thing I can think of is that I liked the LDAP mapping
features of externalauth better then the core features.

Feel free to use the patch if you think it is in any way useful. My
apologies if I have copied it from someone else, but I honestly don’t
remember how I got to this point :slight_smile:

Cheers,
Dave

4

Running

git diff 0.08…0.09 | grep -i environment

in the rt-authen-externalauth git repo doesn’t find me any results.
Did you perhaps have a local mod?

If you’re referring to REMOTE_USER that’s something that RT handles
without an extension.

-kevin

Wow, OK. Apparently I need to work on my documentation a bit more.

It adds configurable element for an environment variable that contains
a username to be trusted. From memory my plans were to use webauth
eventually via the apache module/plugin.

The only thing I can think of is that I liked the LDAP mapping
features of externalauth better then the core features.

Feel free to use the patch if you think it is in any way useful. My
apologies if I have copied it from someone else, but I honestly don’t
remember how I got to this point :slight_smile:

What you could do is auth with mod_auth_kerb or some other apache mod
and then use the info features of RT-Authen-ExternalAuth to pull info
from REMOTE_USER. I believe there is an open bug about that with a
fix in the repo but unreleased.

-kevin