linotp.controllers.selfservice module¶
- selfservice controller - This is the controller for the self service interface,
where users can manage their own tokens
All functions starting with /selfservice/user… are data functions and protected by the session key i.e. the session key must be passed as the parameter session=
-
class
linotp.controllers.selfservice.
SelfserviceController
(*args, **kw)[source]¶ Bases:
linotp.lib.base.BaseController
-
assign
()[source]¶ In this form the user may assign an already existing Token to himself. For this, the user needs to know the serial number of the Token.
-
authUser
= None¶
-
custom_style
()[source]¶ In case the user hasn’t defined a custom css, Pylons calls this action. Return an empty file instead of a 404 (which would mean hitting the debug console)
-
form_access_methods
= ['activateocratoken', 'assign', 'custom_style', 'delete', 'disable', 'enable', 'getotp', 'history', 'index', 'landing', 'load_form', 'reset', 'resync', 'setmpin', 'setpin', 'unassign', 'webprovisiongoogletoken', 'webprovisionoathtoken']¶
-
load_form
()[source]¶ This shows the enrollment form for a requested token type.
implicit parameters are:
Parameters: - type – token type
- scope – defines the rendering scope
Returns: rendered html of the requested token
-
logout
()[source]¶ handle the logout
we delete the cookies from the server and the client and redirect to the login page
-
resync
()[source]¶ In this form, the user can resync an HMAC based OTP token by providing two OTP values
-
setmpin
()[source]¶ In this form the user my set the PIN for his mOTP application soft token on his phone. This is the pin, he needs to enter on his phone, before a otp value will be generated.
-