Endpoint access query not working as expected

[rahul_p]

Hello,

We want to segregate the endpoint visibility according to one attribute but when we are configuring it in the access query then its not working as expected.

In the endpoint access query, we are using :

where users.CUSTOMPROPERTY10='2'

But the endpoint visible to users having below values also :

CUSTOMPROPERTY10='1' or CUSTOMPROPERTY10='0'

One interesting thing is when are using

where users.CUSTOMPROPERTY10='XXXX'

In this case endpoint becomes invisible for all the users.

Please let me know if anyone of you faced such issue.

Regards,

Rahul

[Raghu]

@rahul_p  no it working fine us, could  you re-run micro services job and check it once

[rahul_p]

I did re-run the micro service job multiple times but its the same. Its not working for us.

Thanks!

[rushikeshvartak]

Validate using NEO UI. which does not needed micro service. If does not work share logs

[NM]

Hi @rahul_p it works fine we are using for one of the application.

[rushikeshvartak]

• Use below condition

where users.customroperty10 in ('2')

Validate on NEO request module 

[rahul_p]

Hi @rushikeshvartak ,

This is also not working for us.

Thanks!

[rahul_p · Accepted solution]

Hello,

Access query was satisfying for beneficiary not requestor, so the endpoint was visible for a requestor when requestor requesting for beneficiary who is satisfying the endpoint access query.

When someone/requestor who is not satisfying the criteria requesting for himself/herself then its not visible.

So overall this is working as expected.

Regards,

Rahul