Yes, I just mentioned that jira fixed not yours one even though it is the
same error.
On Oct 8, 2015 8:41 AM, "Lakshani Gamage" wrote:
> Hi Harsha,
>
> I got the same issue in tryit tool of the admin console too.
>
> Thanks,
>
> On Thu, Oct 8, 2015 at 8:28 AM, Harsha
Hi Lakshani,
Can you pull the latest source from git, build the pack again and try this
? since there was a bug and we fixed it.
Thanks
Godwin
On Thu, Oct 8, 2015 at 7:59 AM, Lakshani Gamage wrote:
> Hi Devs,
>
> I defined following XACML policy[1] from latest
Mentioned jira was fixed an issue that is in tryout tool of the admin
console. Your issue should be a different one and need to be check on that.
Adding :Godwin
On Oct 8, 2015 8:00 AM, "Lakshani Gamage" wrote:
> Hi Devs,
>
> I defined following XACML policy[1] from latest
Hi Harsha,
I got the same issue in tryit tool of the admin console too.
Thanks,
On Thu, Oct 8, 2015 at 8:28 AM, Harsha Thirimanna wrote:
> Mentioned jira was fixed an issue that is in tryout tool of the admin
> console. Your issue should be a different one and need to be
Hi Devs,
I defined following XACML policy[1] from latest IS51.0._SNAPSHOT server. I
sent a XACML request[2] to validate against that policy from SoapUI. I
used "getDecision" operation of "EntitlementService" .But I didn't get the
expected response. The response I got is in [3]. But this jira[4]