You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/04/04 13:50:18 UTC

[jira] [Closed] (OPENMEETINGS-972) Default user database

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik closed OPENMEETINGS-972.
-----------------------------------------


> Default user database
> ---------------------
>
>                 Key: OPENMEETINGS-972
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-972
>             Project: Openmeetings
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Yuriy Vasilev
>            Assignee: Maxim Solodovnik
>             Fix For: 3.1.0, 3.0.1
>
>
> Config parameter "ldap_default_id" has no effect in version 3.0.0
> I defined my AD domain as user database in LDAP configuration and set "ldap_default_id=1". But on logon form I see "local DB [internal]" as default.
> In 2.2.0 version I saw my defined domain as default's user database on logon form



--
This message was sent by Atlassian JIRA
(v6.2#6252)