priya jayaraj

Greenhorn
+ Follow
since May 12, 2009
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by priya jayaraj

We have a uri that bound to the namespace say com9. Also, we could see in the log that the request element 'VendorId' prefixed with the required namespace com9 com9:source VendorId='AB', just before it is sent for xacml authorization. So we are stuck on what would be the cause and how and where the prefix is lost. The issue is not reproducible consistently as well (when we restart application servers). It would be great if we get any clues on how to proceed further up with the investigation.

Thanks in advance,
Priya J
Sorry for the typo in the original topic. The status message in the response was

<StatusMessage>error in XPath: Prefix must resolve to a namespace: com9</StatusMessage>

We have a Web Service management tool which does Authentication and Authorization for all the incoming WebService request.
Authorization is based on the rules that are configured for the appropriate service.
We also have XPath specification as part of rule configuration.

We have a rule configured as mentioned below
TestService authoized to the user of the particular group (TestGroup1) and XPath (\\com9:source[@VendorId='AB'])

When we tried accessing the Test Service and received the following response despite giving a valid user (TestUser1 belonging to TestGroup1) and the proper XML element [com9:source VendorId='AB'] in the request.

<Response>
<Result ResourceID="http://testHost:testPort/TestService">
<Decision>Indeterminate</Decision>
<Status>
<StatusCode Value="urn:oasis:names:tc:xacml:1.0:status:processing-error"/>
<StatusMessage>error in XPath: Prefix must resolve to a namespace: com7</StatusMessage>
</Status>
</Result>
</Response>

Xacml Authorization is done with the help of sunxacml.jar. API 'PDP.evaluate(RequestCtx)' is invoked and
We got the above mentioned response. We came to know that the Decision 'Indeterminate' comes if any exception occurs during authorization.

It would be very helpful if we get to know the rootcause of the decision 'Indeterminate' in the above mentioned scenario and the possible scenarios to get 'Indeterminate' decision.

Thanks in advance,
With regards,
Priya.
Hi All,

We have a WSM(Webservice Management Application) product which will generate a 'Proxy WSDL URL' for a 'Real WSDL URL' and it does security/auditing/logging/routing and other stuffs at runtime while getting a webservice request (on Proxy WSDL) and route it to the Functional(Real WSDL URL - Application server where the actual webservice is deployed) endpoint.
On receiving response from the functional endpoint, it again comes back to WSM which has to just give the response back to the user unless and until some special policies are attached (like schema validation policy - it will validate the response body based on the schema XSD)



Here, while reading the response (from functional/application endpoint) over the wire and at the time of creating the actual SoapResponse (XmlResponse) for the end user
xercesImpl.jar is used to parse the data -lsParser.parse(lsInput); which is throwing the exception "org.w3c.dom.ls.LSException: An invalid XML character (Unicode: 0x16) was found in the element content of the document" when it sees not properly formatted XML at any cause (having incompatible data/special character).



As the exception does not even give enough information like where the XML is corrupt/having incompatible data/special character, we cant have a control to do anything from our application/product side ,as it is third party jar xercesImpl.jar. It would be really very helpful if we

> either get a option/boolean to turn off the validation logic which is done internally in xercesImpl.jar at the time of parsing 'lsParser.parse(lsInput);'

> or get additional information in the exception (original cause - like the incompatible/special character (or) a full corrupted response in the exception itself) with which we can get a clue to resolve the issue.



Thanks in Advance

Priya

The XPI is written to copy dlls/xxx.so on the client m/c that will be loaded dynamically into memory as part of applet initialization

Applet initialization will check whether XPI is installed (or) not and if not installed, the user will get redirected to the page that has a link to XPI installation.

On completion of XPI installation, Firefox 3.0.x will give a pop up to 'Restart Firefox'.

I accessed the page(xxx.jsp) that has a applet with a above mentioned logic written in applet initialization.
I got redirected to the page that has link for XPI installation. On completion of XPI installation got a popup
to 'Restat Firefox'
I have noticed that the applet(java) process will not be closed/shutdown even after restarting the Firefox with 'Restart Firefox' option.

After restarting the Firefox, Firefox is getting crashed with a core dump log when accessing any page that has applet in it.

Faced the issue with Java 1.5 and with java 1.6 as well.

The same scenario is working fine in Windows platform(Windows XP).

Did anyone face this issue before. If so, please share your thoughts and suggestions to resolve this issue.

Thanks and Regards
Priya J
14 years ago