This interface represents authorization back end which is responsible for storing informations about existing domains and users.
Usually this interface implementations does not create any entries in a file system. They operate only on a specified database.
This interface is used by ivq implementations. You should not use it directly. If you think that some feature should be added to ivq please contact developers or add them and send us a patch.
This is an implementation of iauth interface. It operates on a PostgreSQL database.
It stores all informations in a database. Doesn't create or use any files other than configuration.
It is represented by pgsqlauthd daemon.
This is an implementation of iauth interface. It operates on a database through JDBC connection. This means that it should be possible to use any database which has an JDBC driver.
It stores all informations in a database. Doesn't create or use any files other than configuration.
It is represented by jdbcauthd daemon.
Note: At this time JDBCAuth is only tested with PostgreSQL database. You can use with other databases but there are some requirements: database must support stored procedures and views. Please, share with us your schemas for other databases.