RTC authentication using OSLC
When posting an XML request using OSLC to RTC v3.0.1 server via FireFox Poster, it appears that the RTC server is not accepting the user/password specified in the Poster dialog. The response (200 OK) we get is the following. However, if I authenticate to RTC first in a FF browser session, then Poster works fine and I get a OSLC response (201) because it is using the authenticated session from browser instead. So, it appears that our RTC server is not accepting BASIC AUTH from the Poster dialog. Because of this issue, our integration program is also failing with the same behavior as well. We need to know how to pass authentication credential programmatically.
<DOCTYPE>
<Licensed>
<html>
<head>
<meta>
<meta>
<title></title>
<link>
<link>
<style>
#net-jazz-ajax-NoScriptMessage {
width: 100%;
color: #D0D0D0;
font-size: 2em;
text-align: center;
position: absolute;
top: 1%;
z-index: 999;
}
</style>
</head>
<body>
<noscript><div>Javascript is either disabled or not available in your Browser</div></noscript>
<div>Loading...</div>
<div></div>
<script>
djConfig = {
isDebug: false,
usePlainJson: true,
baseUrl: "/ccm/web/dojo/",
locale: "en-us",
localizationComplete: true
};
/*null*/
net = {jazz: {ajax: {}}};
net.jazz.ajax._contextRoot = "/ccm";
net.jazz.ajax._webuiPrefix = "/web/";
</script>
<script></script>
<script>
/* <CDATA> */
</script>
<script>
/* <CDATA> */
</script>
</body>
</html>
<DOCTYPE>
<Licensed>
<html>
<head>
<meta>
<meta>
<title></title>
<link>
<link>
<style>
#net-jazz-ajax-NoScriptMessage {
width: 100%;
color: #D0D0D0;
font-size: 2em;
text-align: center;
position: absolute;
top: 1%;
z-index: 999;
}
</style>
</head>
<body>
<noscript><div>Javascript is either disabled or not available in your Browser</div></noscript>
<div>Loading...</div>
<div></div>
<script>
djConfig = {
isDebug: false,
usePlainJson: true,
baseUrl: "/ccm/web/dojo/",
locale: "en-us",
localizationComplete: true
};
/*null*/
net = {jazz: {ajax: {}}};
net.jazz.ajax._contextRoot = "/ccm";
net.jazz.ajax._webuiPrefix = "/web/";
</script>
<script></script>
<script>
/* <CDATA> */
</script>
<script>
/* <CDATA> */
</script>
</body>
</html>
One answer
I am by no means a WAS expert (far from it), but I think that authentication is essentially an application attribute, so it's basically the web.xml files you need to update. (There are some extra things for Tomcat that are mentioned in the articles you referenced.)
The tricky thing about WAS is that it caches copies of an application's war file contents in a few places, so you can't just edit one file to make a change. There is an (old) article on how to make changes to the web.xml file for an application deployed in WAS at https://jazz.net/library/article/76
Sorry I can't give you more specific steps. You can always create a support request if you don't feel like experimenting.
The tricky thing about WAS is that it caches copies of an application's war file contents in a few places, so you can't just edit one file to make a change. There is an (old) article on how to make changes to the web.xml file for an application deployed in WAS at https://jazz.net/library/article/76
Sorry I can't give you more specific steps. You can always create a support request if you don't feel like experimenting.
Comments
1 vote
Comments
John Vasta
FORUM MODERATOR / JAZZ DEVELOPER Mar 27 '13, 9:03 a.m.Gary Dang
Mar 27 '13, 9:11 a.m.Gary Dang
Mar 27 '13, 9:05 a.m.John Vasta
FORUM MODERATOR / JAZZ DEVELOPER Mar 27 '13, 9:15 a.m.