- 3.2Login
- 3.2.1Anonymous user access
- 3.2.2Login providers
3.2Login
The login section provide the configuration space for:
- anonymous user access
- login providers
3.2.1Anonymous user access
By default, the access for anonymous user is disabled. It can be enabled by clicking on the toggle at the right (see screenshot below):
As a standard behaviour, the anonymous user don’t have access to any project. The access can be enabled globally, by toggling the “Global Access” option or by enabling it in a per project basis in the project configuration section.
Additionally, the search functionality can be enabled for the anonymous users by toggling the “Enable Search” entry.
3.2.2Login providers
Lavagna support multiple providers at the same time. In this section they can be enabled and configured.
3.2.2.1Demo
The demo provider must not be selected in production, as the password is the username. It can be useful for a small test round for evaluating the product.
3.2.2.2Ldap
If the users are stored in a ldap directory (Active Directory is supported too), the ldap provider must be configured.
It requires a user that can query the directory (the Manager DN and Manager Password).
The query is composed by a base (Search base) and the filter (User search filter), where {0}
is the placeholder for the username.
The configuration can be tested in the “Verify” form.
3.2.2.3Persona
Mozilla Persona is the simplest external provider available to configure.
The default Audience value is most likely correct.
3.2.2.4Oauth
The application support 4 external oauth providers: bitbucket, github, google, twitter.
Select the oauth provider of the first account and provide the api key and secret. The provided callback url should be the correct one that must be provided.
See the documentation for:
- bitbucket
- github. Registration page is https://github.com/settings/applications/new
- google: the “Google+ API” must be enabled