[rt-users] Problem with login when we using https://

Adrian Stel adisan82 at gmail.com
Fri Jul 29 04:00:40 EDT 2011


Hi,

it does not matter where I click, RT always  log me off.

this is only two of the many examples:

https://rt.ige.psnc.pl/rt/Search/Build.html
https://rt.ige.psnc.pl/rt/Prefs/Other.html

Yes certs works great. When I have CN = RT user name, I will be log in
automatically, problem appears when you try use https:// with CN <> RT
user name and use your user/pass.

Any Idea ?


Best Regards

2011/7/21 Kevin Falcone <falcone at bestpractical.com>:
> On Thu, Jul 21, 2011 at 10:10:31AM +0200, Adrian Stel wrote:
>> Hi Kevin,
>>
>> link after log in:
>> https://rt.ige.psnc.pl/rt/
>>
>> link after log off depends on where I click:
>> https://rt.ige.psnc.pl/rt/Search/Build.html
>> https://rt.ige.psnc.pl/rt/Prefs/Other.html
>
> Is it any link that logs you off, or in particular those two?
> I also note that you say that you're using SSL certs but falling back
> to internal auth.  Are the SSL certs ever working?  If not, it's
> entirely possible that RT is clearing your cooking on every page
> because you've told it to get the REMOTE_USER from your SSL certs.
>
> -kevin
>
>> this is log:
>> [Thu Jul 21 08:06:28 2011] [info]: Successful login for adisan from
>> 150.254.149.220
>> (/usr/share/request-tracker3.8/lib/RT/Interface/Web.pm:430)
>> [Thu Jul 21 08:06:29 2011] [error]: gpg: error reading key: public key
>> not found (/usr/share/request-tracker3.8/lib/RT/Crypt/GnuPG.pm:2115)
>> [Thu Jul 21 08:06:29 2011] [error]: gpg: error reading key: public key
>> not found (/usr/share/request-tracker3.8/lib/RT/Crypt/GnuPG.pm:2115)
>> [Thu Jul 21 08:07:12 2011] [info]: Successful login for adisan from
>> 150.254.149.220
>> (/usr/share/request-tracker3.8/lib/RT/Interface/Web.pm:430)
>> [Thu Jul 21 08:07:13 2011] [warning]: Resolver RT::URI::fsck_com_rt
>> could not parse fsck.com-rt://IGE /ticket/99
>> (/usr/share/request-tracker3.8/lib/RT/URI.pm:147)
>> [Thu Jul 21 08:07:13 2011] [warning]: Resolver RT::URI::fsck_com_rt
>> could not parse fsck.com-rt://IGE /ticket/100
>> (/usr/share/request-tracker3.8/lib/RT/URI.pm:147)
>> [Thu Jul 21 08:07:13 2011] [warning]: Resolver RT::URI::fsck_com_rt
>> could not parse fsck.com-rt://IGE /ticket/99
>> (/usr/share/request-tracker3.8/lib/RT/URI.pm:147)
>> [Thu Jul 21 08:07:13 2011] [warning]: Resolver RT::URI::fsck_com_rt
>> could not parse fsck.com-rt://IGE /ticket/100
>> (/usr/share/request-tracker3.8/lib/RT/URI.pm:147)
>> [Thu Jul 21 08:07:13 2011] [warning]: Resolver RT::URI::fsck_com_rt
>> could not parse fsck.com-rt://IGE /ticket/99
>> (/usr/share/request-tracker3.8/lib/RT/URI.pm:147)
>>
>> Adrian
>>
>> 2011/7/20 Kevin Falcone <falcone at bestpractical.com>:
>> > On Wed, Jul 20, 2011 at 01:35:22PM +0200, Adrian Stel wrote:
>> >> we have strange problem, we are using certificates for authentication
>> >> to RT. User name in RT should be the same as your CN. The problem is
>> >> if we have different user name and using https://, in normal case we
>> >> should be able to use user/pass. And we are, but until we click on any
>> >> link. After that we will be automatically logged off.
>> >
>> > Please provide the link before and after the click that logs you off.
>> > You also should provide your configuration and relevant logs.
>> >
>> > -kevin
>> >
>> >
>> > --------
>> > 2011 Training: http://bestpractical.com/services/training.html
>> >
>>
>>
>>
>> --
>> Pozdrawiam
>> Adrian Stelmaszyk
>>
>> --------
>> 2011 Training: http://bestpractical.com/services/training.html
>
>
> --------
> 2011 Training: http://bestpractical.com/services/training.html
>



-- 
Pozdrawiam
Adrian Stelmaszyk



More information about the rt-users mailing list