User able to see another user's info

[Yurii Orishchuk]

Hi Jake,

Yes, that does not matter what is in this field in your case.

In this location is default value.

You override this value in the service datasource mapping. Thus this value will not be used.

Regards.

[Jake Hare7049642]

I shared the troopsDB so you should be able to see it now.

I had the problem happen again today. This new user:

Created two items while logged in and instead of his acl showing up it showed up like this, even though the other two items he made(the first two) were fine. I've had this problem several times now...:

Please help, this is a very serious problem. Thanks!

[Jake Hare7049642]

Any updates on this? I know it's the weekend so sorry for the rush

[obullei]

Hello!

We are working on this problem.
Please, wait.

[Jake Hare7049642]

Sounds good, thanks!!

[Yurii Orishchuk]

Hi Jake,

Unfortunatly i can's see you DB shared with us.

Please provide us screen shot with DB sharing. Like this: http://prntscr.com/4ii846/direct

Also i see that you have two good items and one with default ACL. May be you have use this create service in other place? Or make some item modification with passing default ACL value? http://prntscr.com/4ii8ym/direct

Regards.

[Jake Hare7049642]

Hi Yurii,

Thanks for the help. See screenshot below. That was my fault; I had the app but not the DB shared.

Regarding your question about the ACL; no, there is only one place in my app where this create service is used. Is there any way to avoid the default ACL being used?

[Yurii Orishchuk]

Hi Jake,

I've checked your DB but can't to see any incorrect data in ACL field.

See details: http://prntscr.com/4ij0hq/direct

Also i've checked your app on "addTroop" page and it seem to bee ok.

So at this time we need steps to reproduce this problem(what we have to do to see item with wrong ACL in Db collection.).

Regards.

[Jake Hare7078781]

The reason you don't see any incorrect data in acl field is because I manually fixed it before my users got mad that their data was being seem by others.

If for some reason the default acl value was being used when it shouldn't is there any way to change the default acl to ("*"(read:false))?
If so where would I do that?

[Yurii Orishchuk]

Hi Jake,

There is no way to change ACL field instead of using needed value in service create/update settings.

Please notify us if you will have steps to reproduce the problem to get your problem. We will take a look.

Regards.