Administration web interface and REST API for freeradius 3 build in django & python. Supports captive portal authentication, WPA Enerprise (802.1x), freeradius rlm_rest, social login, Hotspot 2.0 / 802.11u, importing users from CSV, registration of new users and more.
This new feature does not take into account users who do not have a last_login date.
If a user is created manually or does not follow the standard flow, it is possible that the account will never be used but will never be deleted by these features.
In case the last_login is not available we can use the date_joined field.
2. Unverifying does not take into account RegisteredUser.method
Something I had not thought about before: if a user is manually created, flagging them as not verified will most likely going to prevent them from using their account, they will not be able to verify it again as it happens with mobile phone or payment.
Therefore we need to exclude the following methods from this query: unspecified, manually created and email.
Why not just filter for mobile phone? Because the list of methods is extended by other modules.
1.
last_loginThis new feature does not take into account users who do not have a last_login date.
If a user is created manually or does not follow the standard flow, it is possible that the account will never be used but will never be deleted by these features.
In case the
last_loginis not available we can use thedate_joinedfield.2. Unverifying does not take into account
RegisteredUser.methodSomething I had not thought about before: if a user is manually created, flagging them as not verified will most likely going to prevent them from using their account, they will not be able to verify it again as it happens with mobile phone or payment.
Therefore we need to exclude the following methods from this query: unspecified, manually created and email. Why not just filter for mobile phone? Because the list of methods is extended by other modules.