#81: authreg system should support better authorization
-------------------+--------------------------------------------------------
Reporter: sxw | Owner: smoku
Type: defect | Status: new
Priority: major | Component: General
Version: 2.1 | Blocking:
-------------------+--------------------------------------------------------
At the moment the authreg plugin system doesn't have any support for
authorization. Whilst user_exists() could be used as an authorization
mechanism, there are situations where it is appropriate to know that a
user exists in the authentication database, but not to allow them to
access a service. The authorization check should also be seperate from any
password checks, so that users which are authenticated through mechanisms
that don't use passwords (such as SASL GSSAPI or EXTERNAL) can also be
authorized.
An authorization system could be used with any of the authreg backends
that use an external datasource such as PAM (where calling the pam_account
stack would be appropriate) or LDAP (where the user's membership of a
particular set of LDAP groups could be verified).
I'd like to propose creating a new authreg callback to provide
authorization. As always, I'm happy to write the code if this approach
sounds reasonable.
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/81>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
