It's all about the answers!

Ask a question

Authentication for each work item in web view


Dave Draeger (4172) | asked Aug 07 '07, 6:38 p.m.
I just got LDAP authentication working for the tomcat version of the Team
Server, and noticed a strange quirk. I haven't dug into it a lot but was
wondering if this is a potential bug. When using the web view and doing a
query to show work items, it appears that every graphic that appears in the
work item list, a new LDAP request is made... so as the page is being
displayed in my browser, I can see requests in the tomcat log going out to
LDAP.

I don't see this same behaviour when using the Eclipse client to do the same
work items query.

Have others seen this or is this a known issue with the web interface?
Essentially, everything still works, but it will put an unneeded strain on
the LDAP server for all the requests.

--
Dave Draeger
IBM WebSphere Serviceability Development

One answer



permanent link
Richard Backhouse (6661) | answered Aug 08 '07, 1:24 p.m.
JAZZ DEVELOPER
The problem lies with how Tomcat communicates with the LDAP server. It
has no form of caching and thus your LDAP server will get flooded with
authentication requests.

An alternative solution is use IHS as a proxy front end. IHS does
support authentication request caching. This is how the Jazz
Self-hosting server is setup.

Richard


Dave Draeger wrote:
I just got LDAP authentication working for the tomcat version of the Team
Server, and noticed a strange quirk. I haven't dug into it a lot but was
wondering if this is a potential bug. When using the web view and doing a
query to show work items, it appears that every graphic that appears in the
work item list, a new LDAP request is made... so as the page is being
displayed in my browser, I can see requests in the tomcat log going out to
LDAP.

I don't see this same behaviour when using the Eclipse client to do the same
work items query.

Have others seen this or is this a known issue with the web interface?
Essentially, everything still works, but it will put an unneeded strain on
the LDAP server for all the requests.

Your answer


Register or to post your answer.