Reference¶
Public API functions¶
-
aiohttp_security.setup(app, identity_policy, autz_policy)[source]¶ Setup
aiohttpapplication with security policies.Parameters: - app – aiohttp
aiohttp.web.Applicationinstance. - identity_policy – indentification policy, an
AbstractIdentityPolicyinstance. - autz_policy – authorization policy, an
AbstractAuthorizationPolicyinstance.
- app – aiohttp
-
coroutine
aiohttp_security.remember(request, response, identity, **kwargs)[source]¶ Remember identity in response, e.g. by storing a cookie or saving info into session.
The action is performed by registered
AbstractIdentityPolicy.remember().Usually the identity is stored in user cookies somehow for using by
authorized_userid()andpermits().Parameters: - request –
aiohttp.web.Requestobject. - response –
aiohttp.web.StreamResponseand descendants likeaiohttp.web.Response. - identity (str) –
aiohttp.web.Requestobject. - kwargs –
additional arguments passed to
AbstractIdentityPolicy.remember().They are policy-specific and may be used, e.g. for specifiying cookie lifetime.
- request –
-
coroutine
aiohttp_security.forget(request, response)[source]¶ Forget previously remembered identity.
The action is performed by registered
AbstractIdentityPolicy.forget().Parameters: - request –
aiohttp.web.Requestobject. - response –
aiohttp.web.StreamResponseand descendants likeaiohttp.web.Response.
- request –
Checker that doesn’t pass if user is not authorized by request.
Parameters: request – aiohttp.web.Requestobject.Return str: authorized user ID if success Raise: aiohttp.web.HTTPUnauthorizedfor anonymous users.Usage:
async def handler(request): await check_authorized(request) # this line is never executed for anonymous users
-
coroutine
aiohttp_security.check_permission(request, permission)[source]¶ Checker that doesn’t pass if user has no requested permission.
Parameters: request – aiohttp.web.Requestobject.Raise: aiohttp.web.HTTPUnauthorizedfor anonymous users.Raise: aiohttp.web.HTTPForbiddenif user is authorized but has no access rights.Usage:
async def handler(request): await check_permission(request, 'read') # this line is never executed if a user has no read permission
Retrieve userid.
The user should be registered by
remember()before the call.Parameters: request – aiohttp.web.Requestobject.Returns: struserid orNonefor session without signed in user.
-
coroutine
aiohttp_security.permits(request, permission, context=None)[source]¶ Check user’s permission.
Return
Trueif user remembered in request has specified permission.Allowed permissions as well as context meaning are depends on
AbstractAuthorizationPolicyimplementation.Actually it’s a wrapper around
AbstractAuthorizationPolicy.permits()coroutine.The user should be registered by
remember()before the call.Parameters: - request –
aiohttp.web.Requestobject. - permission – Requested permission.
strorenum.Enumobject. - context – additional object may be passed into
AbstractAuthorizationPolicy.permission()coroutine.
Returns: Trueif registered user has requested permission,Falseotherwise.- request –
-
coroutine
aiohttp_security.is_anonymous(request)[source]¶ Checks if user is anonymous user.
Return
Trueif user is not remembered in request, otherwise returnsFalse.Parameters: request – aiohttp.web.Requestobject.
-
@aiohttp_security.login_required[source]¶ Decorator for handlers that checks if user is authorized.
Raises
aiohttp.web.HTTPUnauthorizedif user is not authorized.Deprecated since version 0.3: Use
check_authorized()async function.
-
@aiohttp_security.has_permission(permission)[source]¶ Decorator for handlers that checks if user is authorized and has correct permission.
Raises
aiohttp.web.HTTPUnauthorizedif user is not authorized.Raises
aiohttp.web.HTTPForbiddenif user is authorized but has no access rights.Parameters: permission (str) – requested permission. Deprecated since version 0.3: Use
check_authorized()async function.
Abstract policies¶
- aiohttp_security is built on top of two abstract policies –
AbstractIdentityPolicyandAbstractAuthorizationPolicy.
The first one responds on remembering, retrieving and forgetting identity into some session storage, e.g. HTTP cookie or authorization token.
The second is responsible to return persistent userid for session-wide identity and check user’s permissions.
Most likely sofware developer reuses one of pre-implemented identity policies from aiohttp_security but build authorization policy from scratch for every application/project.
Identification policy¶
-
class
aiohttp_security.AbstractIdentityPolicy[source]¶ -
coroutine
identify(request)[source]¶ Extract identity from request.
Abstract method, should be overriden by descendant.
Parameters: request – aiohttp.web.Requestobject.Returns: the claimed identity of the user associated request or Noneif no identity can be found associated with the request.
-
coroutine
remember(request, response, identity, **kwargs)[source]¶ Remember identity.
May use request for accessing required data and response for storing identity (e.g. updating HTTP response cookies).
kwargs may be used by concrete implementation for passing additional data.
Abstract method, should be overriden by descendant.
Parameters: - request –
aiohttp.web.Requestobject. - response –
aiohttp.web.StreamResponseobject or derivative. - identity – identity to store.
- kwargs – optional additional arguments. An individual identity policy and its consumers can decide on the composition and meaning of the parameter.
- request –
-
coroutine
forget(request, response)[source]¶ Forget previously stored identity.
May use request for accessing required data and response for dropping identity (e.g. updating HTTP response cookies).
Abstract method, should be overriden by descendant.
Parameters: - request –
aiohttp.web.Requestobject. - response –
aiohttp.web.StreamResponseobject or derivative.
- request –
-
coroutine
Authorization policy¶
-
class
aiohttp_security.AbstractAuthorizationPolicy[source]¶