[
https://issues.apache.org/jira/browse/OPENMEETINGS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik closed OPENMEETINGS-113.
-----------------------------------------
Assignee: Maxim Solodovnik
Closing all old 'Resolved' issues
> Define a default Login-Domain (ie an Ldap domain) to be automatically
> selected in the frontend login window
> -----------------------------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-113
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
> Project: Openmeetings
> Issue Type: Improvement
> Affects Versions: 2.0 Apache Incubator Release
> Environment: N/A
> Reporter: Thibault Le Meur
> Assignee: Maxim Solodovnik
> Priority: Minor
> Labels: ldap, loginmodule
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: ldap_default_id.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When an administrator defines an LDAP "domain", his users are likely to
> authenticate against it and not against the default "Internal DB" that is
> automatically selected in the login window.
> This is not an issue for users already defined as LDAP users in the internal
> DB because OM is able to read the LDAP domain from teh DB in order to
> perfform authentication.
> However this is an issue for the first login because most users would forget
> to set the Domain and thus would fail to login for the first time (resulting
> in multiple calls to the It service... and I would definitely like to avoid
> this situation ;-) .
> I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
