Misago
  • Introduction
  • Setup
    • Create server on Digital Ocean
    • Point domain at your server
    • Setup Misago on your Server
    • Upgrading your Misago to latest version
  • Settings
    • Accessing settings
    • Static settings reference
    • Dynamic settings reference
  • Coding style
  • GDPR Compliance Guide
  • Social authentication
  • User rank styles
  • Category styles
  • User authentication
  • Writing new admin actions
  • Permissions framework
  • View decorators
  • Context processors
  • Frontend context
  • Audit trail
  • Forms
  • Cache
  • Sending mails
  • Markup
  • Posting process
  • Profile fields
  • Threads types
  • Extending pages
  • Validating registrations
  • Validators
  • Search filters
  • Template tags
  • Shortcuts
  • View errors
  • Locales
Powered by GitBook
On this page
  • misago.admin.auth.is_admin_session(request)
  • misago.admin.auth.start_admin_session(request, user)
  • misago.admin.auth.update_admin_session(request)
  • misago.admin.auth.close_admin_session(request)
  • Testing Admin views using test client
  • misago.admin.testutils.admin_login(client, username, password)

User authentication

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_staff set 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_EXPIRATION setting, 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.auth module and misago.admin.middleware.AdminAuthMiddleware middleware. Middleware uses methods from auth to detect if request is pointed at protected namespace, and if it is, it uses facilities to handle and control state of administrators session.

misago.admin.auth.is_admin_session(request)

Returns true if current request has valid administrator session. Otherwhise returns false.

misago.admin.auth.start_admin_session(request, user)

Promotes current session to state of administrator session.

misago.admin.auth.update_admin_session(request)

Updates last activity timestamp on admin session.

misago.admin.auth.close_admin_session(request)

Closes current admin session, degrading it to "casual" session and keeps user signed in.

Testing Admin views using test client

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_login function for this purpose.

misago.admin.testutils.admin_login(client, username, password)

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:index link that should result with admin login form for unauthenticated users.

PreviousCategory stylesNextWriting new admin actions

Last updated 7 years ago