Re: [sunxacml-discuss] sunxacml policy evaluation problem

[Ashok S. <as...@sf...>]

Hello Seth,

Thanks for the response.

I made a class to generate the RequestCtx object. Because I use the same  
class to test with both policies (policy in the file and the policy  
generated by the policy builder) it is unlikely that there are any  
additional space or typos.

Also, I manually inspected both policies, generated by the policy builder  
class, and the policy in the file. Both are same.

Help is really appereciated.

Thanks,

Ashok.

I was doing some debugging, it seems that
On Mon, 07 Mar 2005 22:10:03 -0500, Seth Proctor <Set...@Su...>  
wrote:

>
> Hi Ashok. Sorry for the delay...I've had to ignore most XACML stuff for  
> the last few days. Anyway..
>
> I'm not sure exactly what's going wrong. Like you said, the policy is  
> being found, but in processing it you're getting an error. Specifically,  
> you're seeing:
>
>> <Response>
>>   <Result ResourceId="java.html">
>>     <Decision>Indeterminate</Decision>
>>     <Status>
>>       <StatusCode  
>> Value="urn:oasis:names:tc:xacml:1.0:status:processing-error"/>
>>        
>> <StatusMessage>urn:oasis:names:tc:xacml:1.0:function:string-one-and- 
>> only expects a bag that contains a single element, got a bag with 0  
>> elements</StatusMessage>
>>     </Status>
>>   </Result>
>> </Response>
>
> Which means that when the PDP (or, more accurately, the context handler)  
> tried to resolve a value for the attribute "group" it came up empty. Are  
> you sure you're using exactly the same Request with both the generated  
> and the parsed policies? If the Requests are exactly the same, then I'm  
> not entirely sure why you're seeing this error.
>
> The only other thing I can think of off the top of my head is that  
> you've added some whitespace or changed the case of your text somewhere,  
> but I don't see any evidence of this. Basically, the error message  
> you're seeing should indicate that the attribute was resolved correctly,  
> but it had no values defined in the Request. Strange. Double-check that  
> you're using exactly the same Request in both cases, and then let me  
> know if you're still seeing trouble and I'll see how I can help.
>
>
> seth
>
>



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/