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/06/17 15:41:03 UTC
[jira] [Resolved] (OPENMEETINGS-442) om LDAP users controlled with
a group
[ https://issues.apache.org/jira/browse/OPENMEETINGS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-442.
-------------------------------------------
Fix Version/s: 3.0.3
Resolution: Fixed
Assignee: Maxim Solodovnik
LDAP is fully refactored:
Committed revision 1603163.
Please file new issues in case anything is wrong
> om LDAP users controlled with a group
> -------------------------------------
>
> Key: OPENMEETINGS-442
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-442
> Project: Openmeetings
> Issue Type: New Feature
> Components: LDAP
> Affects Versions: 2.0.0 Apache Incubator Release
> Environment: Debian 6
> Reporter: Renaud Fortier
> Assignee: Maxim Solodovnik
> Fix For: 3.0.3, 3.1.0
>
>
> Because we don't want everybody on our LDAP servers (Active Directory) can loggin on our openMeetings server, I set the configuration default_group_id and default_domain_id to "0" (wrong value). Then, if a user log in our server for the first time, the user got an empty page and he can do nothing. But now I can't assign the real organisation to my LDAP users because I got errors or it doesn't save the profile correctly.
> Anyway, it would be great to control who can access our server by an Active Directory group.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)