The identitiy of a user is authenticated after his login.
The identity and the method he was
The aspect of authentication is configured in the
subsection Authentication
of the AAAA
section
in the server configuration.
In order to use authentication in Wolframe you have to configure the
loading of the module implementing it. The authentication mech explained
here as example is implemented in the module mod_auth_textfile.
For using it you have to declare the module mod_auth_textfile
in the LoadModules
section of your configuration before.
The following table shows the configuration settings for Authentication in Wolframe.
Table 4.1. Authentication configuration settings
Name | Parameter | Description |
---|---|---|
RandomDevice | address or path | Specifies the random device to be used. This configuration setting is optional. The system should have a reasonable default for most applications. |
Textfile | section | Specifies the block with the configuration for authentication based on a textfile with WOLFRAME-CRAM as authentication mech. |
The following example shows an Authentication
configuration with the Wolframe textfile authentication module
that provides an authentication over the "WOLFRAME-CRAM" protocol:
AAAA { Authentication { randomDevice /dev/urandom TextFile { identifier "TextFileAuth" file /var/tmp/wolframe.auth } }
Currently only the authentication protocol for
WOLFRAME-CRAM
is implemented. The
client can choose between no authentication
(if configured to allow no authentication)
or WOLFRAME-CRAM
. You configure
it as shown in the example above. For the setup of a
client see the chapter "Clients".
Copyright © 2014 - Project Wolframe - All Rights Reserved