Creating ticket dependent on browser!

Hello,

Using RT 3.8.10 on Solaris with Authentication against Microsoft Active Directory, I’ve encountered an odd behaviour.

I’ve allowed the users to create tickets in one queue (by granting SeeQueue and CreateTicket).

When I try to create the ticket with my account (which BTW is RT superuser) with Internet Explorer 8, it works.

With the same user under Firefox (18.0), it doesn’t work, the queue is simply not displayed in the scrollable menu when you want to choose the destination queue !

I even compared the source code and the only difference is the presence (on IE8) and absence (on FF) of a couple of lines :

Queue2

Any idea how to debug this ? Could something be corrupt in the user profile ?

Thanks in advance.

Loïc Mahé

Toulouse, France

Hi,

Rich Text Editor that is shipped with RT 3.8 doesn’t work with FF 18.
Try to google archives. I think we have a fix, but can not find it and
don’t have time to dig more :)On Wed, Jan 16, 2013 at 7:28 PM, Loic.Mahe@rsi.fr wrote:

Hello,

Using RT 3.8.10 on Solaris with Authentication against Microsoft Active
Directory, I’ve encountered an odd behaviour.

I’ve allowed the users to create tickets in one queue (by granting SeeQueue
and CreateTicket).

When I try to create the ticket with my account (which BTW is RT superuser)
with Internet Explorer 8, it works.

With the same user under Firefox (18.0), it doesn’t work, the queue is
simply not displayed in the scrollable menu when you want to choose the
destination queue !

I even compared the source code and the only difference is the presence (on
IE8) and absence (on FF) of a couple of lines :

Queue2

Any idea how to debug this ? Could something be corrupt in the user profile
?

Thanks in advance.

Loïc Mahé

Toulouse, France

Best regards, Ruslan.

Rich Text Editor that is shipped with RT 3.8 doesn’t work with FF 18.
Try to google archives. I think we have a fix, but can not find it and
don’t have time to dig more :slight_smile:

Ruz - Assuming you’re thinking of this


That was in 3.8.10.

For the original author:

Using RT 3.8.10 on Solaris with Authentication against Microsoft Active
Directory, I’ve encountered an odd behaviour.

When I try to create the ticket with my account (which BTW is RT superuser)
with Internet Explorer 8, it works.

With the same user under Firefox (18.0), it doesn’t work, the queue is
simply not displayed in the scrollable menu when you want to choose the
destination queue !

How are you doing the auth? mod_auth_kerb? RT-Authen-ExternalAuth?
Please note that on 3.8 we cached queues aggressively, so if you are
picking up an existing session on FF you’d get a stale queue list.

-kevin

Hello,

Authentication is done with RT::Authen::ExternalAuth.

I had to fully empty FF’s cache in order to have a correct queue list in the ticket creation. All is fine now.

Maybe an entry in the FAQ could mention this ?
Are queues still cached in RT 4.x ?

Thanks for your answers and have a nice day.

Loïc Mahé
Toulouse, France
-----Message d’origine-----
Envoyé : mercredi 16 janvier 2013 21:56
Loïc Mahé

Toulouse, France

Rich Text Editor that is shipped with RT 3.8 doesn’t work with FF 18.
Try to google archives. I think we have a fix, but can not find it and
don’t have time to dig more :slight_smile:

Ruz - Assuming you’re thinking of this


That was in 3.8.10.

For the original author:

Using RT 3.8.10 on Solaris with Authentication against Microsoft Active
Directory, I’ve encountered an odd behaviour.

When I try to create the ticket with my account (which BTW is RT superuser)
with Internet Explorer 8, it works.

With the same user under Firefox (18.0), it doesn’t work, the queue is
simply not displayed in the scrollable menu when you want to choose the
destination queue !

How are you doing the auth? mod_auth_kerb? RT-Authen-ExternalAuth?
Please note that on 3.8 we cached queues aggressively, so if you are
picking up an existing session on FF you’d get a stale queue list.

-kevin

Authentication is done with RT::Authen::ExternalAuth.

I had to fully empty FF’s cache in order to have a correct queue list in the ticket creation. All is fine now.

I suspect emptying the cache just cleared out your cookie and forced a
reload.

Maybe an entry in the FAQ could mention this ?
Are queues still cached in RT 4.x ?

This was a frequently asked question in 2010, but since the
introduction of RT 4 (where I wrote code to avoid most of the queue
caching problems) it comes up infrequently.

-kevin