MODX Manager - Always Redirects back to login

Just thought I would share what the solution was to this issue for us.

When we tried to log-in to the manager we were redirected back to the log-in screen over and over.

We’d recently experienced some downtime on our server due to a hardware issue.

I checked the error.log in /core/cache/logs and found this line:

’.\<database name here>\modx_session’ is marked as crashed and should be repaired

We therefore had to repair the table (we did so using MySQL Administrator) and hey presto normal service resumed.

Hi,

I was having this problem too. It was because my development vm's time/date was out of sync with my host OS - due to my closing my laptop and putting my host OS to sleep.

An 'instant fix' for anyone having the same issue is to re-sync your clock via ntpdate:



After running this command my manager login returned to normal behaviour immediately.

I recommend running ntp as a daemon to automatically correct for this situation:

It's also possible this can be avoided by installing vmware tools / parallels tools , not sure.

I got the same issue, all suggestions above for me not working, so I started digging.
May be it's happening due to DB caching of sessions, I coudn't verify it.

But I healed all problems this way:

• Backup old database with replace option except [tableprefix]_system_settings table
  Removed all files inside core/cache
  Dropped all tables in database, or whole database.
  Make a New install from folder where modx is installed
  Restore a backup, and it's all working flawlessly.

Made it on revo 2.1.7.

Would be nice to have a settings reseting for such situations, or another fallback machnism to access manager with bad settings. [ed. note: danpiel last edited this post 14 years, 9 months ago.]

I'm getting this redirect to login behaviour with: MODX Revolution 2.2.0-pl2 (traditional)
Environment:
PHP Version 5.2.17
Apache/2.2.3 (CentOS)

I can login fine with the default admin account though extra admin accounts added cannot login.
Sessions have been cleared, tried on multiple browsers, added php_value session.auto_start 0 to .htaccess, repaired sessions table etc etc etc.

I've had this now on separate installations, on different servers, with this version of Modx.

What gives?

Are the other admins in the Administrator group or another group?

Are you sure they have permission to log in?


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODX info for everyone: http://bobsguides.com/modx.html

Hi Bob,

Are you sure they have permission to log in?

This got me to thinking, I'm a recent Evo convert so still learning the ropes - I checked out the user group: administrator | role: member. Updated role to: super user and can now login with the new account.
So role "member" assigned to administrator group doesn't have login permission?

It's complicated. No user has permission to log in to the Manager unless they belong to a User Group with a Context Access ACL permission (with a Context of 'mgr') that has a policy that allows it -- and they have the minimum role in the group to qualify for that policy.

As a general practice, I recommend *not* putting other admin users in the Administrator group because it will make things easier to understand and will give you more Form Customization options.

Here's what I'd recommend:


Duplicate the Administrator Policy
Create a role for the other admin users with an Authority number of 10.
Create a User Group for them
Put them in the users group (and remove them from the Administrator group)
In Security -> Access Controls, right-click on the user group and select "Update User Group"
On the Context Access tab, add a new ACL entry with the following values:

Context: mgr
Minimum Role: (their role)
Policy: (the duplicate policy you created)

Save.

Flush permissions
Flush all sessions

They should be able to log in at that point.

Then, edit the duplicate policy and uncheck any permissions they shouldn't have.
Save and flush again.


More info here: http://bobsguides.com/revolution-permissions.html




---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODX info for everyone: http://bobsguides.com/modx.html

Thanks very much Bob for the clear explanation

Is it just me or is this security approach overly complicated and highly unintuitive?