When the site is set to offline mode, cram.js proceeds halfway through the login and then stops. This is because anything besides /user is unavailable when in offline mode to anonymous users.

I'm not sure how to make the challenge number available (embed it in the user login page?) but regardless the javascript should fail and let the user know if they want to proceed with an insecure login.

Comments

selmanj’s picture

selmanj commented

I think I know the solution to this. Rather than retrieving challenge numbers via a URL like it is currently done (which fails when the site is in offline mode), challenge numbers should be embedded into the login form. I was worried about doing this at first because I was afraid all the session numbers would get eaten up when the login block is enabled, but now that I think about it, it makes sense to just assign a challenge number to a session variable, and instead of getting a new one on each page view, use the old one until the user either logs in, or fails to log in.

selmanj’s picture

selmanj commented
Status: Active » Fixed

Fixed! Now you can log in even when in maintenance mode.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.