HTTP 302 (Found) Error in RTC Client
Using RTC 1.0 Beta2 on Windows and Server 1.0 Beta2 on Linux RHEL5, with:
WAS 6.1
DB2 9.5
Federated LDAP
The server is using a self-signed SSL certificate
I edited the web.xml as documented the TeamServer Setup Guide in "Manage
Jazz Security" section, to turn on security. The Web UI continued to
work as before but the RTC IDE couldn't connect at all; kept getting
HTTP 302 errors no matter what userid/password I used.
Could the use of a self-signed SSL cert be causing problems like this ?
If I revert the web.xml file back to defaults like so:
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/secure/*</url-pattern>
</web-resource-collection>
then the RTC IDE can login with any password (!!!) although the userid
must be defined. The RTC IDE is using a URI like:
https://servername:9443/jazz/
Any help appreciated
WAS 6.1
DB2 9.5
Federated LDAP
The server is using a self-signed SSL certificate
I edited the web.xml as documented the TeamServer Setup Guide in "Manage
Jazz Security" section, to turn on security. The Web UI continued to
work as before but the RTC IDE couldn't connect at all; kept getting
HTTP 302 errors no matter what userid/password I used.
Could the use of a self-signed SSL cert be causing problems like this ?
If I revert the web.xml file back to defaults like so:
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/secure/*</url-pattern>
</web-resource-collection>
then the RTC IDE can login with any password (!!!) although the userid
must be defined. The RTC IDE is using a URI like:
https://servername:9443/jazz/
Any help appreciated
9 answers
pravesh@us.ibm-dot-com.no-spam.invalid (pravesh) wrote in news:fm6a8i$9e$1
@localhost.localdomain:
Seems everyone who used my doc has the 302 problem
So I will pretend the issue is mine :)
Let me dig into it and ask my friends in WAS support what they believe
happens
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
@localhost.localdomain:
Has anyone figured this out yet?
Seems everyone who used my doc has the 302 problem
So I will pretend the issue is mine :)
Let me dig into it and ask my friends in WAS support what they believe
happens
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
"Mark D. Parry" <parrym@us.ibm.com> wrote in
news:478E77A2.8070407@us.ibm.com:
Nope unfortunatly :(
Well, I should not say that, I made progress in finding symptoms but I do
not know why
example: Shawn has a WAS setup and when I connect to http://
<shawn>:9080/jazz the URL stay the same, I get prompted for uid/password
in the nice form logging
When I do that on my machine (http://localhost:9080/jazz) the url is
redirected to https://localhost:9443/jazz/auth/authrequired in my browser
(I can see the url) and I get an ugly form logging
I believe this redirect in the URL is the cause of the 302
Also I noticed (and it may be related or not) that I get some error
related to Proxy$8 when I log in the web...
Can you correlate any of the symptoms ? Are you seeing the same ?
PS: I got the latest RTC client and server, also upgraded WAS to 6.1.0.13
My feeling is thart it is not a JAZZ issue but a WebSphere setup issue :
( Because it seems we hit the 302 before we hit any jazz code.. but yet
again... I may be wrong :(
I asked 2 colleagues from WAS support... will see what they have to say
tomorrow ... sorry about that
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
news:478E77A2.8070407@us.ibm.com:
Hi Christophe,
Just wondering if you've made any progress on this issue, both me
and
another colleague hit it today. Thanks...
--Mark
Nope unfortunatly :(
Well, I should not say that, I made progress in finding symptoms but I do
not know why
example: Shawn has a WAS setup and when I connect to http://
<shawn>:9080/jazz the URL stay the same, I get prompted for uid/password
in the nice form logging
When I do that on my machine (http://localhost:9080/jazz) the url is
redirected to https://localhost:9443/jazz/auth/authrequired in my browser
(I can see the url) and I get an ugly form logging
I believe this redirect in the URL is the cause of the 302
Also I noticed (and it may be related or not) that I get some error
related to Proxy$8 when I log in the web...
Can you correlate any of the symptoms ? Are you seeing the same ?
PS: I got the latest RTC client and server, also upgraded WAS to 6.1.0.13
My feeling is thart it is not a JAZZ issue but a WebSphere setup issue :
( Because it seems we hit the 302 before we hit any jazz code.. but yet
again... I may be wrong :(
I asked 2 colleagues from WAS support... will see what they have to say
tomorrow ... sorry about that
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
Christophe Elek <Christophe.Elek@gmail.com> wrote in
news:Xns9A27AC43E10D1celekcaibmcom@199.246.40.53:
Proxy issues are because I do not have the proper level of the SDK so the
issue is 'unrelated' to the 302 we are facing
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
news:Xns9A27AC43E10D1celekcaibmcom@199.246.40.53:
Also I noticed (and it may be related or not) that I get some error
related to Proxy$8 when I log in the web...
Proxy issues are because I do not have the proper level of the SDK so the
issue is 'unrelated' to the 302 we are facing
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
Hi Christophe,
Just wondering if you've made any progress on this issue, both me and
another colleague hit it today. Thanks...
--Mark
Christophe Elek wrote:
Just wondering if you've made any progress on this issue, both me and
another colleague hit it today. Thanks...
--Mark
Christophe Elek wrote:
pravesh@us.ibm-dot-com.no-spam.invalid (pravesh) wrote in news:fm6a8i$9e$1
@localhost.localdomain:
Has anyone figured this out yet?
Seems everyone who used my doc has the 302 problem
So I will pretend the issue is mine :)
Let me dig into it and ask my friends in WAS support what they believe
happens
David Ward <davidward@us.ibm.com> wrote in news:fm113j$n6r$1
@localhost.localdomain:
After speing some times troubleshooting, I came to the same conclusion as
development.... but later :D
https://jazz.net/jazz/web/projects/Jazz%
20Project#action=com.ibm.team.workitem.viewWorkItem&id=41135
This means the next milestone should contain a simple way to fully and
simply secure the WAR file
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
@localhost.localdomain:
Any help appreciated
After speing some times troubleshooting, I came to the same conclusion as
development.... but later :D
https://jazz.net/jazz/web/projects/Jazz%
20Project#action=com.ibm.team.workitem.viewWorkItem&id=41135
This means the next milestone should contain a simple way to fully and
simply secure the WAR file
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
Christophe,
To summarize, updating the web.xml as such:
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/secure/*</url-pattern>
<url-pattern>/service/*</url-pattern>
<url-pattern>/resource/*</url-pattern>
<url-pattern>/events/*</url-pattern>
<url-pattern>/resources/*</url-pattern>
<url-pattern>/users/*</url-pattern>
<url-pattern>/projects/*</url-pattern>
<url-pattern>/indexing-rules/*</url-pattern>
</web-resource-collection>
solves the issue of the ugly login form for the WebUI, it does not solve the issue of not being able to connect using RTC because the 302 issue still remains and is being tracked here:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35379
Is that correct?
This is the behavior I'm seeing after the web.xml update. Are there any work arounds for this as I'm completely blocked right now.
To summarize, updating the web.xml as such:
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/secure/*</url-pattern>
<url-pattern>/service/*</url-pattern>
<url-pattern>/resource/*</url-pattern>
<url-pattern>/events/*</url-pattern>
<url-pattern>/resources/*</url-pattern>
<url-pattern>/users/*</url-pattern>
<url-pattern>/projects/*</url-pattern>
<url-pattern>/indexing-rules/*</url-pattern>
</web-resource-collection>
solves the issue of the ugly login form for the WebUI, it does not solve the issue of not being able to connect using RTC because the 302 issue still remains and is being tracked here:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35379
Is that correct?
This is the behavior I'm seeing after the web.xml update. Are there any work arounds for this as I'm completely blocked right now.
There seem to be issues with form based auth and WAS. I have added a
comment to this workitem documenting a workaround.
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35379
Richard Backhouse
Jazz WebUI and Server
pravesh wrote:
comment to this workitem documenting a workaround.
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35379
Richard Backhouse
Jazz WebUI and Server
pravesh wrote:
Christophe,
To summarize, updating the web.xml as such:
web-resource-collection
web-resource-name>secure</web-resource-name
url-pattern>/secure/*</url-pattern
url-pattern>/service/*</url-pattern
url-pattern>/resource/*</url-pattern
url-pattern>/events/*</url-pattern
url-pattern>/resources/*</url-pattern
url-pattern>/users/*</url-pattern
url-pattern>/projects/*</url-pattern
url-pattern>/indexing-rules/*</url-pattern
/web-resource-collection
solves the issue of the ugly login form for the WebUI, it does not
solve the issue of not being able to connect using RTC because the
302 issue still remains and is being tracked here:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35379
Is that correct?
This is the behavior I'm seeing after the web.xml update. Are there
any work arounds for this as I'm completely blocked right now.
RTC 3.0
Mozilla Firefox 3.6.13
Getting "Problem loading page" error.
IN the "Tools -> Options -> Settings", if "No Proxy" option is selected the web client works fine. but if I choose "automatic proxy configuration url" and enter the path to the *.pac file, I can browse the net but jazz login page fails with the below message. Any thoughts?
The proxy server is refusing connections
Firefox is configured to use a proxy server that is refusing connections.
* Check the proxy settings to make sure that they are correct.
* Contact your network administrator to make sure the proxy server is working.
Mozilla Firefox 3.6.13
Getting "Problem loading page" error.
IN the "Tools -> Options -> Settings", if "No Proxy" option is selected the web client works fine. but if I choose "automatic proxy configuration url" and enter the path to the *.pac file, I can browse the net but jazz login page fails with the below message. Any thoughts?
The proxy server is refusing connections
Firefox is configured to use a proxy server that is refusing connections.
* Check the proxy settings to make sure that they are correct.
* Contact your network administrator to make sure the proxy server is working.