I'm actually out on vacation, but this looks like you don't have the
correct account and password to bind to AD, or the account doesn't
have access to the object info.
As a test, try an account and pass that have higher privileges and see
if that works.
On Mar 2, 3:57 pm, Danny Trinh wrote:
> Th
The error is different:
ERROR 03-02 14:56:37.488 LdapAuthBase.java 25333 209
org.openmeetings.app.ldap.LdapAuthBase [NioProcessor-1] - Error
occured on LDAP Search : [LDAP: error code 1 - : LdapErr:
DSID-0C090627, comment: In order to perform this operation a
successful bind must be complet
Try without encryption to eliminate it as a possibility. We are
currently not using crypto (we run this on a closed network.)
On Mar 2, 1:55 pm, Danny Trinh wrote:
> I tried both userPrincipalName and sAMAccountName, both produce
> similar errors. It seemed that LDAP didn't transfer MD5 crypt pa
I tried both userPrincipalName and sAMAccountName, both produce
similar errors. It seemed that LDAP didn't transfer MD5 crypt password
correctly. I also use both Crypt-types that mention in
http://code.google.com/p/openmeetings/wiki/CustomCryptMechanism. I
think I missed some thing else. Any idea?
This is a known-good configuration. Try this and see if the UPN works.
Then if it does, you can try experimenting. I don't think you will get
sAMAccountName to work yet, because the code doesn't look for that.
ldap_server_type=LDAP
#LDAP URL
# does a DNS lookup for Domain Controllers (if your DNS
I also tried UPN (email address), but it said invalid password.
[ERROR] [NioProcessor-1] org.openmeetings.app.data.user.Usermanagement
- dtr...@eastonbellsports.com not authenticated.
WARN 03-01 19:58:41.296 MainService.java 2045275 254
org.openmeetings.app.remote.MainService [NioProcessor-1] - lo
I used LDAP config below:
ldap_server_type=OpenLDAP
ldap_conn_url=ldap://10.1.1.100:389
ldap_admin_dn=CN:openfire,OU:Service Accounts,OU:
Administrators,OU:ccc,DC:,DC:c,DC:loc
ldap_passwd=openfire3
ldap_search_base=DC:LOC
field_user_principal=sAMAccountName (I want to use this inst
Yes, we have it working. Unless the OM team gets to it first, we will
put together an extension to the LDAP classes to create and populate
organisations in OM based on AD group membership. We also need to be
able to restrict logins based on AD group memebership.
One minor bug with the LDAP auth is
Below are what I have installed to try LDAP:
[r...@l2dev ~]# rpm -qa |grep ldap | sort
apr-util-ldap-1.3.9-2.fc12.x86_64
krb5-server-ldap-1.7.1-2.fc12.x86_64
ldapjdk-4.18-5.fc12.x86_64
mozldap-6.0.5-6.fc12.i686
mozldap-6.0.5-6.fc12.x86_64
mozldap-devel-6.0.5-6.fc12.i686
mozldap-devel-6.0.5-6.fc12.x
I had similar issues with Centos. Which ldap rpms do you have
installed? You will need some or all of the following:
mozldap-6.0.5-1.el5
ldapjdk-4.18-2jpp.3.el5
openldap-2.3.43-3.el5
openldap-clients-2.3.43-3.el5
Or the Fedora equivalents.
--
You received this message because you are subscribed
Looking at the code there is no way to assoicate an AD user with and
organization.
Unless everyone is put in default which doesn't look like the case.
When there is
no organization it will login the user but the dashboard will fail to
show.
LDAP code should allow setting group attributes from A
I modified the om_ldap.cfg according to Smoeker's advised, but I still
got errors (see below). I looked deeper in errors and noticed that
it's trying to read LdapAuthBase.java, LdapLoginManagement.java, etc
in openmeetings.jar, red5.jar, etc., but seeing none. Am I missing
something that makes java
hola,
first of all : at the moment, there's no relation between the OM
organization and a Ldap Group at all.
-> means : if LDAP Auth is on and a user logs in successfully for the
first time, his userdata is written to local database and he gets
added to the default organization u added on install
I use sAMAccountName for userID, and memberOf for group (extract CN in
memberOf to get group name). Also, openfire has used the following to
collect the data from AD:
ldap.adminDN openfire
ldap.adminPassword openfire1
ldap.autoFollowAliasReferrals true
ldap.autoFollowReferrals false
ldap.baseDN
What are the attributes that you are using fro group and userid. They
are different that the default on many Ad deployments.
On Feb 25, 4:45 pm, Danny Trinh wrote:
> Below is my ldap config:
>
> ldap_server_type=OpenLDAP
> ldap_conn_url = ldap://10.10.10.10:389/?sAMAccountName?sub?(objectClass=
Below is my ldap config:
ldap_server_type=OpenLDAP
ldap_conn_url = ldap://10.10.10.10:389/?sAMAccountName?sub?(objectClass=user)
ldap_admin_dn=CN:openfire,DC:b,DC:c,DC:loc
ldap_passwd=openfire1
ldap_search_base=DC:b,DC:c,DC:LOC
field_user_principal=userPrincipalName
ldap_auth_typ
hi,
that box should be not shown at all.
Oliver has made the LDAP Connector, also against ADS. Maybe he has the tipp
to solve that.
Sebastian
2010/2/25 Danny Trinh
> Hi Sebastian,
>
>
> On Feb 25, 12:30 pm, Sebastian Wagner wrote:
> > What do you mean by *I can't see "organisation"*
> > you h
What do you mean by *I can't see "organisation"*
you have the box of organizations but no chose to actually take anything?
Sebastian
2010/2/25 Danny Trinh
> It seemed to be working but it's not. When I read all document and
> discussion about LDAP on this forum + wiki, I started setup OM to
>
Hi Sebastian,
On Feb 25, 12:30 pm, Sebastian Wagner wrote:
> What do you mean by *I can't see "organisation"*
> you have the box of organizations but no chose to actually take anything?
>
Yes, I saw the box of organization, but there is nothing to choose.
Regarding of LDAP, I believe we just h
It seemed to be working but it's not. When I read all document and
discussion about LDAP on this forum + wiki, I started setup OM to
connect to Windows AD. So I can integrate all AD's users to this OM.
The results are OM can't collect data from AD.
Here what I did:
- Setup fedora 64 and install all
20 matches
Mail list logo
