[ACL] why do I get error Code: 200 OK for user - My Forums

[ACL] why do I get error Code: 200 OK for user

pierrot1010 — Sep 03, 2017, 09:21 PM

Dear All,

I just installed and setup a MODX2.5.7 web site and I now setup ACL permission following that procedure
https://docs.modx.com/revolution/2.x/administering-your-site/security/security-tutorials/giving-a-user-manager-access

I flushed the permission.

Now when I log with an user account with edit permission, after selecting a ressource, I receive that error messge

Code: 200 OK
{"success":false,"message":"Autorisation refus\u00e9e !","total":0,"data":[],"object":[]}

I surfed into the MODX forum I found serveral solution. Those solution work for the forum topic owner.
https://forums.modx.com/thread/92206/error-code-200-ok-on-every-resource-select?page=2#dis-post-507407
https://forums.modx.com/thread/?thread=92387&page=3
One of them what to check and select view_user and class_map. I also red to change the setting compress_css and compress_js to false.

Even if I tried those solution, it did not solve my issue. Did I missed something?

I would like to point out, this issue happen only for user with edit permission. For my admin account, I do not experience that issue.

So, I wunder, if you would have another solution to help me to solve it

Many that for your support
Cheers

Re: [ACL] why do I get error Code: 200 OK for user (Best Answer)

pierrot1010 — Sep 04, 2017, 02:54 PM

Thank a lot, Mark!!!!! That solved my problem!!!

I checked 'view_templates'
I logged out the user
I cleaned cache and emptied /core/cache
I logged user and .... solved!!

Thank!!

Re: [ACL] why do I get error Code: 200 OK for user (Best Answer)

markh — Sep 04, 2017, 02:47 PM

The view_templates permission is also required for an editor user, make sure that one is ticked as well.

There was a change (caused by me, sorry ) in 2.5.1 or 2.5.2 where some actions were assigned a new permission. That was meant to combat a security issue, but had the side effect of requiring a new permission in some cases. That explains why you would not have that problem on an older site with the same permission set (though you really must update that ASAP, the security issues fixed in 2.5.2 are quite severe).

It's highly unlikely that a .htaccess file causes that error, but that's easy to disprove. Simply rename it to something else for a moment and verify that the problem is still present.

Re: [ACL] why do I get error Code: 200 OK for user

pierrot1010 — Sep 04, 2017, 02:30 PM

this thing I do not understand.

I previously build a web site with MODx 2.5.1 and I do have that issue. I compare all setting and policies and all seams to be egal.

The difference between two site, 2.5.1 is in two language and the actual web site 2.5.7 has only one language

Can this problem come from the .htaccess file? (I configure URL friendly for both but the htaccess is a bit difference as I am using Babel for the multilanguage...

I become creasy )

Re: [ACL] why do I get error Code: 200 OK for user

pierrot1010 — Sep 04, 2017, 12:44 PM

Hello
Thank for your support,

I granted the user with sudo
I flush the permission and I cleaned the cache from
I unlog all users
I deleted /core/cache
I logged with the user and I still have this error message (

However, when I check the sudo check box for the user, the problem is solved. Thank!

But I do not want to keep her as sudo. Any idea what I need to change in my policy?

Re: [ACL] why do I get error Code: 200 OK for user

lkfranklin — Sep 04, 2017, 04:23 AM

From my experience with this it's usually due to disallowing permission to something that is still being loaded on the resources. I often find it an easier process to first create a custom form manager that removes the fields and tabs I don't want the user to be able to edit and then go in and selectively disable permissions with ACL.

Re: [ACL] why do I get error Code: 200 OK for user

BobRay — Sep 04, 2017, 03:48 AM

This may not help, but flushing permissions alone is not enough. You also have to flush sessions (log everyone out) after making any permission changes. And if you're changes aren't taking effect, it doesn't hurt to also delete all files in the core/cache directory.

To see if this is really a MODX permissions issue, temporarily make the user a sudo user. If that solves it, it's definitely a MODX permission issue.

Another good technique is to temporarily change the policy to a duplicate of the Administrator Policy for Context Access ACL entries, or a duplicate of the Resource policy for Resource Group Access ACL entries. If that fixes things, you can then start unchecking permissions in the policy until it breaks down. That will tell you which permission was missing.