Misago adds additional layer of security around admin areas in your site. This means that unless you've signed to admin area directly, you have to authenticate yourself one more time to upgrade your session from "casual" one to "administrator".
This mechanism was put in place because it's common for forum administrators to browse and use forums while signed on their administrator account. By default, Django requires user to be signed in and have special
is_staffset on his or her account and know the path to administration backend to administrate site, which is good approach for situations when staff accounts are used exclusively for administration and not day to day usage.
In addition for re-authentication requirement, Misago also monitors inactivity periods between requests to admin interfaces, and if one exceeds length specified in
MISAGO_ADMIN_SESSION_EXPIRATIONsetting, it will assume that administrator has been inactive and request another reauthentication upon next request to admin backend.
Implementation in this mechanism is placed within
misago.admin.middleware.AdminAuthMiddlewaremiddleware. Middleware uses methods from
authto detect if request is pointed at protected namespace, and if it is, it uses facilities to handle and control state of administrators session.
Returns true if current request has valid administrator session. Otherwhise returns false.
Promotes current session to state of administrator session.
Updates last activity timestamp on admin session.
Closes current admin session, degrading it to "casual" session and keeps user signed in.
To test protected admin views from within your test cases, you have to open valid admin session for test client. Misago provides
misago.admin.testutils.admin_loginfunction for this purpose.
This function will make provided test client instance use valid admin session during test requests. Note that internally this function makes POST request to
misago:admin:indexlink that should result with admin login form for unauthenticated users.