Re: Error on Working Userdata
;-)
if ur a familiar with Java/eclipse i would recommend debugging the
application while running on localhost (thats surely the fastest
method to see, how changes take effect without the need to re-deploy
the application after compiling)
-> otherwise u could become a "sysout" - debugger by writing
logmessages within sourcecode and check values at runtime ;-) that way
affords compiling and re-deploying the application.
u should start debugging directly after login at function doLdapLogin.
After successful login, more detaildata is searched for the user by
calling
Vector> result = lAuth.getData
(ldap_search_scope, ldap_search_filter, attributes);
if this Vector has the size of 0 or > 1, u would see a valid
logmessage, so we assume, you are receiving One valid record for your
login user.
-> this users Ldap data can be monitored by using
HashMap userData = result.get(0);
Iterator iter = userData.keySet().iterator();
while(iter.hasNext()){
String key = iter.next();
String val = userData.get(key);
log.debug("Key : " + key + ", Val:" + val);
}
-> Checkout the result (and comapre to a working result...)
see ya
Smoeker
On 8 Jan., 15:33, maillist sev wrote:
> hmm ok.. done so..
> changed the file to this:
> public static final String LDAP_KEY_LASTNAME = "sn";
> public static final String LDAP_KEY_FIRSTNAME = "givenName";
> public static final String LDAP_KEY_MAIL = "mail";
> public static final String LDAP_KEY_STREET = "description";
> public static final String LDAP_KEY_ADDITIONAL_NAME = "description";
> public static final String LDAP_KEY_FAX =
> "facsimileTelephoneNumber";
> public static final String LDAP_KEY_ZIP = "postalCode";
> public static final String LDAP_KEY_COUNTRY = "streetAddress";
> public static final String LDAP_KEY_TOWN = "description";
> public static final String LDAP_KEY_PHONE = "telephoneNumber";
> only for testing of course
> description is set with de
> --> same error
> :-(
> More ideas?
>
> On 8 Jan., 14:55, smoeker wrote:
>
> > hola,
>
> > u can either follow the build instructions from the openMeetings
> > project page or run one of the antscripts (e.g. build_red5webapp.xml)
>
> > see ya
>
> > Smoeker
>
> > On 8 Jan., 14:32, maillist sev wrote:
>
> > > hmm I've tested to add every field for one user..
>
> > > result: the field "co" is not allowed for the scheme.
> > > What can i do now?
>
> > > On 8 Jan., 14:27, maillist sev wrote:
>
> > > > > -> if u want to debug that, u could sysout the userdata within that
> > > > > function and check, if some values are emtpy and if they are requiered
> > > > > for creating a user object (nullable column?)
>
> > > > --> Great: How can i do this?
>
> > > > The Login of the User is successful (Typing a wrong password produces
> > > > a error <-- that's right :-) )
>
> > > > I really want to show more of the log-file, but there is not more
> > > > information :-(
> > > > The Configuration looks like this:
>
> > > > #ConfigurationFile for LDAP Auth
> > > > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of
> > > > OM and point to this file
> > > > #o.becherer,14.01.2009
> > > > #specify the LDAP Server type
> > > > ldap_server_type=OpenLDAP
> > > > #LDAP URL
> > > > ldap_conn_url=ldap://10.4.148.96:1389
> > > > #Login distinguished name (DN) for Authentification on LDAP Server -
> > > > keep emtpy if not requiered
> > > > ldap_admin_dn=cn:service-user,dc:domain,dc:de
> > > > #Loginpass for Authentification on LDAP Server - keep emtpy if not
> > > > requiered
> > > > ldap_passwd=password_for_user
> > > > #base to search for userdata(of user, that wants to login
> > > > ldap_search_base=ou:users,dc:e-domain,dc:de
> > > > # Fieldnames (can differ between Ldap servers)
> > > > field_user_principal=uid
> > > > # Ldap auth type(SIMPLE,NONE)
> > > > ldap_auth_type=SIMPLE
>
> > > > AND: It's an OpenLDAP!
>
> > > > This Configurations are set in our LDAP:
> > > > sn, givenName, mail..
> > > > the other values are mostly not set, so that every other field should
> > > > result in null.
>
> > > > Thanks for your help...
>
> > > > On 8 Jan., 14:01, smoeker wrote:
>
> > > > > hola,
>
> > > > > the internal OM User gets created based on the data retrieved via LDAP
> > > > > Lookup (in case of succesful login).
>
> > > > > please show us more of the logfile to identify a possible reason for
> > > > > the nullpointer
>
> > > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata
> > > > > detail search have to differ. Within Code, the following LdapFields
> > > > > are mapped :
>
> > > > > public static final String LDAP_KEY_LASTNAME = "sn";
> > > > > public static final String LDAP_KEY_FIRSTNAME = "givenName";
> > > > > public static final String LDAP_KEY_MAIL = "mail";
> > > > > public static final String LDAP_KEY_STREET = "streetAddress";
> > > > > public static final
Re: Error on Working Userdata
hmm ok.. done so.. changed the file to this: public static final String LDAP_KEY_LASTNAME = "sn"; public static final String LDAP_KEY_FIRSTNAME = "givenName"; public static final String LDAP_KEY_MAIL = "mail"; public static final String LDAP_KEY_STREET = "description"; public static final String LDAP_KEY_ADDITIONAL_NAME = "description"; public static final String LDAP_KEY_FAX = "facsimileTelephoneNumber"; public static final String LDAP_KEY_ZIP = "postalCode"; public static final String LDAP_KEY_COUNTRY = "streetAddress"; public static final String LDAP_KEY_TOWN = "description"; public static final String LDAP_KEY_PHONE = "telephoneNumber"; only for testing of course description is set with de --> same error :-( More ideas? On 8 Jan., 14:55, smoeker wrote: > hola, > > u can either follow the build instructions from the openMeetings > project page or run one of the antscripts (e.g. build_red5webapp.xml) > > see ya > > Smoeker > > On 8 Jan., 14:32, maillist sev wrote: > > > > > hmm I've tested to add every field for one user.. > > > result: the field "co" is not allowed for the scheme. > > What can i do now? > > > On 8 Jan., 14:27, maillist sev wrote: > > > > > -> if u want to debug that, u could sysout the userdata within that > > > > function and check, if some values are emtpy and if they are requiered > > > > for creating a user object (nullable column?) > > > > --> Great: How can i do this? > > > > The Login of the User is successful (Typing a wrong password produces > > > a error <-- that's right :-) ) > > > > I really want to show more of the log-file, but there is not more > > > information :-( > > > The Configuration looks like this: > > > > #ConfigurationFile for LDAP Auth > > > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of > > > OM and point to this file > > > #o.becherer,14.01.2009 > > > #specify the LDAP Server type > > > ldap_server_type=OpenLDAP > > > #LDAP URL > > > ldap_conn_url=ldap://10.4.148.96:1389 > > > #Login distinguished name (DN) for Authentification on LDAP Server - > > > keep emtpy if not requiered > > > ldap_admin_dn=cn:service-user,dc:domain,dc:de > > > #Loginpass for Authentification on LDAP Server - keep emtpy if not > > > requiered > > > ldap_passwd=password_for_user > > > #base to search for userdata(of user, that wants to login > > > ldap_search_base=ou:users,dc:e-domain,dc:de > > > # Fieldnames (can differ between Ldap servers) > > > field_user_principal=uid > > > # Ldap auth type(SIMPLE,NONE) > > > ldap_auth_type=SIMPLE > > > > AND: It's an OpenLDAP! > > > > This Configurations are set in our LDAP: > > > sn, givenName, mail.. > > > the other values are mostly not set, so that every other field should > > > result in null. > > > > Thanks for your help... > > > > On 8 Jan., 14:01, smoeker wrote: > > > > > hola, > > > > > the internal OM User gets created based on the data retrieved via LDAP > > > > Lookup (in case of succesful login). > > > > > please show us more of the logfile to identify a possible reason for > > > > the nullpointer > > > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > > > > detail search have to differ. Within Code, the following LdapFields > > > > are mapped : > > > > > public static final String LDAP_KEY_LASTNAME = "sn"; > > > > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > > > > public static final String LDAP_KEY_MAIL = "mail"; > > > > public static final String LDAP_KEY_STREET = "streetAddress"; > > > > public static final String LDAP_KEY_ADDITIONAL_NAME = > > > > "description"; > > > > public static final String LDAP_KEY_FAX = > > > > "facsimileTelephoneNumber"; > > > > public static final String LDAP_KEY_ZIP = "postalCode"; > > > > public static final String LDAP_KEY_COUNTRY = "co"; > > > > public static final String LDAP_KEY_TOWN = "l"; > > > > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > > > > these values work fine for Active Directory e.g. - but for openLdap > > > > the Detail Field names can differ > > > > > -> so it could be possible, that u dont retrieve certaiin values > > > > needed to create a local user. > > > > -> the function createUserFromLdapData checks most of missing values > > > > and replaces it by default values, but it still could be possible, > > > > that an error occurs. > > > > -> if u want to debug that, u could sysout the userdata within that > > > > function and check, if some values are emtpy and if they are requiered > > > > for creating a user object (nullable column?) > > > > > see ya > > > > > Smoeker > > > > > see ya > > > > > On 8 Jan., 13:41, maillist sev wrote: > > > > > > Hello there, > > > > > > today I've successfully configured the LDAP for openmeetings. The > > > > > first two or three users where successfully created in openmeetings. > > > > > But after
Re: Error on Working Userdata
hola, u can either follow the build instructions from the openMeetings project page or run one of the antscripts (e.g. build_red5webapp.xml) see ya Smoeker On 8 Jan., 14:32, maillist sev wrote: > hmm I've tested to add every field for one user.. > > result: the field "co" is not allowed for the scheme. > What can i do now? > > On 8 Jan., 14:27, maillist sev wrote: > > > > -> if u want to debug that, u could sysout the userdata within that > > > function and check, if some values are emtpy and if they are requiered > > > for creating a user object (nullable column?) > > > --> Great: How can i do this? > > > The Login of the User is successful (Typing a wrong password produces > > a error <-- that's right :-) ) > > > I really want to show more of the log-file, but there is not more > > information :-( > > The Configuration looks like this: > > > #ConfigurationFile for LDAP Auth > > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of > > OM and point to this file > > #o.becherer,14.01.2009 > > #specify the LDAP Server type > > ldap_server_type=OpenLDAP > > #LDAP URL > > ldap_conn_url=ldap://10.4.148.96:1389 > > #Login distinguished name (DN) for Authentification on LDAP Server - > > keep emtpy if not requiered > > ldap_admin_dn=cn:service-user,dc:domain,dc:de > > #Loginpass for Authentification on LDAP Server - keep emtpy if not > > requiered > > ldap_passwd=password_for_user > > #base to search for userdata(of user, that wants to login > > ldap_search_base=ou:users,dc:e-domain,dc:de > > # Fieldnames (can differ between Ldap servers) > > field_user_principal=uid > > # Ldap auth type(SIMPLE,NONE) > > ldap_auth_type=SIMPLE > > > AND: It's an OpenLDAP! > > > This Configurations are set in our LDAP: > > sn, givenName, mail.. > > the other values are mostly not set, so that every other field should > > result in null. > > > Thanks for your help... > > > On 8 Jan., 14:01, smoeker wrote: > > > > hola, > > > > the internal OM User gets created based on the data retrieved via LDAP > > > Lookup (in case of succesful login). > > > > please show us more of the logfile to identify a possible reason for > > > the nullpointer > > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > > > detail search have to differ. Within Code, the following LdapFields > > > are mapped : > > > > public static final String LDAP_KEY_LASTNAME = "sn"; > > > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > > > public static final String LDAP_KEY_MAIL = "mail"; > > > public static final String LDAP_KEY_STREET = "streetAddress"; > > > public static final String LDAP_KEY_ADDITIONAL_NAME = > > > "description"; > > > public static final String LDAP_KEY_FAX = > > > "facsimileTelephoneNumber"; > > > public static final String LDAP_KEY_ZIP = "postalCode"; > > > public static final String LDAP_KEY_COUNTRY = "co"; > > > public static final String LDAP_KEY_TOWN = "l"; > > > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > > > these values work fine for Active Directory e.g. - but for openLdap > > > the Detail Field names can differ > > > > -> so it could be possible, that u dont retrieve certaiin values > > > needed to create a local user. > > > -> the function createUserFromLdapData checks most of missing values > > > and replaces it by default values, but it still could be possible, > > > that an error occurs. > > > -> if u want to debug that, u could sysout the userdata within that > > > function and check, if some values are emtpy and if they are requiered > > > for creating a user object (nullable column?) > > > > see ya > > > > Smoeker > > > > see ya > > > > On 8 Jan., 13:41, maillist sev wrote: > > > > > Hello there, > > > > > today I've successfully configured the LDAP for openmeetings. The > > > > first two or three users where successfully created in openmeetings. > > > > But after that (or with a new browser-session on another PC) no new > > > > user was created. > > > > When a user want to log in, everything works fine --> means: > > > > Openmeetings checks if he entered the corrected Login-Information > > > > But after that, no User is created and the following error is shown in > > > > the log...: > > > > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > > > > Working Userdata : null > > > > > I've looked in the code, and this means, the user can't be created. > > > > But why? > > > > > Thanks for your help. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
Re: Error on Working Userdata
hmm ok.. one question: how to quickly compile it? today I'm using the NightlyBuild r2776 with the red5-server. how can i compile it for this server? thanks. On 8 Jan., 14:40, smoeker wrote: > hola, > > u mean : co is not part of your openLdap recordset? > > in that case u should modify the variable > > public static final String LDAP_KEY_COUNTRY = "co"; > > within LdapLoginmanagement and recompile OM. > > -> Afterwards u should retrieve a Country, that will be created if not > existent within OM... > > see ya > > Smoeker > > On 8 Jan., 14:32, maillist sev wrote: > > > > > hmm I've tested to add every field for one user.. > > > result: the field "co" is not allowed for the scheme. > > What can i do now? > > > On 8 Jan., 14:27, maillist sev wrote: > > > > > -> if u want to debug that, u could sysout the userdata within that > > > > function and check, if some values are emtpy and if they are requiered > > > > for creating a user object (nullable column?) > > > > --> Great: How can i do this? > > > > The Login of the User is successful (Typing a wrong password produces > > > a error <-- that's right :-) ) > > > > I really want to show more of the log-file, but there is not more > > > information :-( > > > The Configuration looks like this: > > > > #ConfigurationFile for LDAP Auth > > > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of > > > OM and point to this file > > > #o.becherer,14.01.2009 > > > #specify the LDAP Server type > > > ldap_server_type=OpenLDAP > > > #LDAP URL > > > ldap_conn_url=ldap://10.4.148.96:1389 > > > #Login distinguished name (DN) for Authentification on LDAP Server - > > > keep emtpy if not requiered > > > ldap_admin_dn=cn:service-user,dc:domain,dc:de > > > #Loginpass for Authentification on LDAP Server - keep emtpy if not > > > requiered > > > ldap_passwd=password_for_user > > > #base to search for userdata(of user, that wants to login > > > ldap_search_base=ou:users,dc:e-domain,dc:de > > > # Fieldnames (can differ between Ldap servers) > > > field_user_principal=uid > > > # Ldap auth type(SIMPLE,NONE) > > > ldap_auth_type=SIMPLE > > > > AND: It's an OpenLDAP! > > > > This Configurations are set in our LDAP: > > > sn, givenName, mail.. > > > the other values are mostly not set, so that every other field should > > > result in null. > > > > Thanks for your help... > > > > On 8 Jan., 14:01, smoeker wrote: > > > > > hola, > > > > > the internal OM User gets created based on the data retrieved via LDAP > > > > Lookup (in case of succesful login). > > > > > please show us more of the logfile to identify a possible reason for > > > > the nullpointer > > > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > > > > detail search have to differ. Within Code, the following LdapFields > > > > are mapped : > > > > > public static final String LDAP_KEY_LASTNAME = "sn"; > > > > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > > > > public static final String LDAP_KEY_MAIL = "mail"; > > > > public static final String LDAP_KEY_STREET = "streetAddress"; > > > > public static final String LDAP_KEY_ADDITIONAL_NAME = > > > > "description"; > > > > public static final String LDAP_KEY_FAX = > > > > "facsimileTelephoneNumber"; > > > > public static final String LDAP_KEY_ZIP = "postalCode"; > > > > public static final String LDAP_KEY_COUNTRY = "co"; > > > > public static final String LDAP_KEY_TOWN = "l"; > > > > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > > > > these values work fine for Active Directory e.g. - but for openLdap > > > > the Detail Field names can differ > > > > > -> so it could be possible, that u dont retrieve certaiin values > > > > needed to create a local user. > > > > -> the function createUserFromLdapData checks most of missing values > > > > and replaces it by default values, but it still could be possible, > > > > that an error occurs. > > > > -> if u want to debug that, u could sysout the userdata within that > > > > function and check, if some values are emtpy and if they are requiered > > > > for creating a user object (nullable column?) > > > > > see ya > > > > > Smoeker > > > > > see ya > > > > > On 8 Jan., 13:41, maillist sev wrote: > > > > > > Hello there, > > > > > > today I've successfully configured the LDAP for openmeetings. The > > > > > first two or three users where successfully created in openmeetings. > > > > > But after that (or with a new browser-session on another PC) no new > > > > > user was created. > > > > > When a user want to log in, everything works fine --> means: > > > > > Openmeetings checks if he entered the corrected Login-Information > > > > > But after that, no User is created and the following error is shown in > > > > > the log...: > > > > > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > > > > > Working Userdata : null > > > > > > I've looked in the code, and t
Re: Error on Working Userdata
hola, u mean : co is not part of your openLdap recordset? in that case u should modify the variable public static final String LDAP_KEY_COUNTRY = "co"; within LdapLoginmanagement and recompile OM. -> Afterwards u should retrieve a Country, that will be created if not existent within OM... see ya Smoeker On 8 Jan., 14:32, maillist sev wrote: > hmm I've tested to add every field for one user.. > > result: the field "co" is not allowed for the scheme. > What can i do now? > > On 8 Jan., 14:27, maillist sev wrote: > > > > -> if u want to debug that, u could sysout the userdata within that > > > function and check, if some values are emtpy and if they are requiered > > > for creating a user object (nullable column?) > > > --> Great: How can i do this? > > > The Login of the User is successful (Typing a wrong password produces > > a error <-- that's right :-) ) > > > I really want to show more of the log-file, but there is not more > > information :-( > > The Configuration looks like this: > > > #ConfigurationFile for LDAP Auth > > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of > > OM and point to this file > > #o.becherer,14.01.2009 > > #specify the LDAP Server type > > ldap_server_type=OpenLDAP > > #LDAP URL > > ldap_conn_url=ldap://10.4.148.96:1389 > > #Login distinguished name (DN) for Authentification on LDAP Server - > > keep emtpy if not requiered > > ldap_admin_dn=cn:service-user,dc:domain,dc:de > > #Loginpass for Authentification on LDAP Server - keep emtpy if not > > requiered > > ldap_passwd=password_for_user > > #base to search for userdata(of user, that wants to login > > ldap_search_base=ou:users,dc:e-domain,dc:de > > # Fieldnames (can differ between Ldap servers) > > field_user_principal=uid > > # Ldap auth type(SIMPLE,NONE) > > ldap_auth_type=SIMPLE > > > AND: It's an OpenLDAP! > > > This Configurations are set in our LDAP: > > sn, givenName, mail.. > > the other values are mostly not set, so that every other field should > > result in null. > > > Thanks for your help... > > > On 8 Jan., 14:01, smoeker wrote: > > > > hola, > > > > the internal OM User gets created based on the data retrieved via LDAP > > > Lookup (in case of succesful login). > > > > please show us more of the logfile to identify a possible reason for > > > the nullpointer > > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > > > detail search have to differ. Within Code, the following LdapFields > > > are mapped : > > > > public static final String LDAP_KEY_LASTNAME = "sn"; > > > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > > > public static final String LDAP_KEY_MAIL = "mail"; > > > public static final String LDAP_KEY_STREET = "streetAddress"; > > > public static final String LDAP_KEY_ADDITIONAL_NAME = > > > "description"; > > > public static final String LDAP_KEY_FAX = > > > "facsimileTelephoneNumber"; > > > public static final String LDAP_KEY_ZIP = "postalCode"; > > > public static final String LDAP_KEY_COUNTRY = "co"; > > > public static final String LDAP_KEY_TOWN = "l"; > > > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > > > these values work fine for Active Directory e.g. - but for openLdap > > > the Detail Field names can differ > > > > -> so it could be possible, that u dont retrieve certaiin values > > > needed to create a local user. > > > -> the function createUserFromLdapData checks most of missing values > > > and replaces it by default values, but it still could be possible, > > > that an error occurs. > > > -> if u want to debug that, u could sysout the userdata within that > > > function and check, if some values are emtpy and if they are requiered > > > for creating a user object (nullable column?) > > > > see ya > > > > Smoeker > > > > see ya > > > > On 8 Jan., 13:41, maillist sev wrote: > > > > > Hello there, > > > > > today I've successfully configured the LDAP for openmeetings. The > > > > first two or three users where successfully created in openmeetings. > > > > But after that (or with a new browser-session on another PC) no new > > > > user was created. > > > > When a user want to log in, everything works fine --> means: > > > > Openmeetings checks if he entered the corrected Login-Information > > > > But after that, no User is created and the following error is shown in > > > > the log...: > > > > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > > > > Working Userdata : null > > > > > I've looked in the code, and this means, the user can't be created. > > > > But why? > > > > > Thanks for your help. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at
Re: Error on Working Userdata
hmm I've tested to add every field for one user.. result: the field "co" is not allowed for the scheme. What can i do now? On 8 Jan., 14:27, maillist sev wrote: > > -> if u want to debug that, u could sysout the userdata within that > > function and check, if some values are emtpy and if they are requiered > > for creating a user object (nullable column?) > > --> Great: How can i do this? > > The Login of the User is successful (Typing a wrong password produces > a error <-- that's right :-) ) > > I really want to show more of the log-file, but there is not more > information :-( > The Configuration looks like this: > > #ConfigurationFile for LDAP Auth > #ConfigKey 'ldap_config_path' must be set in DataBase Configration of > OM and point to this file > #o.becherer,14.01.2009 > #specify the LDAP Server type > ldap_server_type=OpenLDAP > #LDAP URL > ldap_conn_url=ldap://10.4.148.96:1389 > #Login distinguished name (DN) for Authentification on LDAP Server - > keep emtpy if not requiered > ldap_admin_dn=cn:service-user,dc:domain,dc:de > #Loginpass for Authentification on LDAP Server - keep emtpy if not > requiered > ldap_passwd=password_for_user > #base to search for userdata(of user, that wants to login > ldap_search_base=ou:users,dc:e-domain,dc:de > # Fieldnames (can differ between Ldap servers) > field_user_principal=uid > # Ldap auth type(SIMPLE,NONE) > ldap_auth_type=SIMPLE > > AND: It's an OpenLDAP! > > This Configurations are set in our LDAP: > sn, givenName, mail.. > the other values are mostly not set, so that every other field should > result in null. > > Thanks for your help... > > On 8 Jan., 14:01, smoeker wrote: > > > > > hola, > > > the internal OM User gets created based on the data retrieved via LDAP > > Lookup (in case of succesful login). > > > please show us more of the logfile to identify a possible reason for > > the nullpointer > > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > > detail search have to differ. Within Code, the following LdapFields > > are mapped : > > > public static final String LDAP_KEY_LASTNAME = "sn"; > > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > > public static final String LDAP_KEY_MAIL = "mail"; > > public static final String LDAP_KEY_STREET = "streetAddress"; > > public static final String LDAP_KEY_ADDITIONAL_NAME = "description"; > > public static final String LDAP_KEY_FAX = > > "facsimileTelephoneNumber"; > > public static final String LDAP_KEY_ZIP = "postalCode"; > > public static final String LDAP_KEY_COUNTRY = "co"; > > public static final String LDAP_KEY_TOWN = "l"; > > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > > these values work fine for Active Directory e.g. - but for openLdap > > the Detail Field names can differ > > > -> so it could be possible, that u dont retrieve certaiin values > > needed to create a local user. > > -> the function createUserFromLdapData checks most of missing values > > and replaces it by default values, but it still could be possible, > > that an error occurs. > > -> if u want to debug that, u could sysout the userdata within that > > function and check, if some values are emtpy and if they are requiered > > for creating a user object (nullable column?) > > > see ya > > > Smoeker > > > see ya > > > On 8 Jan., 13:41, maillist sev wrote: > > > > Hello there, > > > > today I've successfully configured the LDAP for openmeetings. The > > > first two or three users where successfully created in openmeetings. > > > But after that (or with a new browser-session on another PC) no new > > > user was created. > > > When a user want to log in, everything works fine --> means: > > > Openmeetings checks if he entered the corrected Login-Information > > > But after that, no User is created and the following error is shown in > > > the log...: > > > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > > > Working Userdata : null > > > > I've looked in the code, and this means, the user can't be created. > > > But why? > > > > Thanks for your help. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
Re: Error on Working Userdata
> -> if u want to debug that, u could sysout the userdata within that > function and check, if some values are emtpy and if they are requiered > for creating a user object (nullable column?) --> Great: How can i do this? The Login of the User is successful (Typing a wrong password produces a error <-- that's right :-) ) I really want to show more of the log-file, but there is not more information :-( The Configuration looks like this: #ConfigurationFile for LDAP Auth #ConfigKey 'ldap_config_path' must be set in DataBase Configration of OM and point to this file #o.becherer,14.01.2009 #specify the LDAP Server type ldap_server_type=OpenLDAP #LDAP URL ldap_conn_url=ldap://10.4.148.96:1389 #Login distinguished name (DN) for Authentification on LDAP Server - keep emtpy if not requiered ldap_admin_dn=cn:service-user,dc:domain,dc:de #Loginpass for Authentification on LDAP Server - keep emtpy if not requiered ldap_passwd=password_for_user #base to search for userdata(of user, that wants to login ldap_search_base=ou:users,dc:e-domain,dc:de # Fieldnames (can differ between Ldap servers) field_user_principal=uid # Ldap auth type(SIMPLE,NONE) ldap_auth_type=SIMPLE AND: It's an OpenLDAP! This Configurations are set in our LDAP: sn, givenName, mail.. the other values are mostly not set, so that every other field should result in null. Thanks for your help... On 8 Jan., 14:01, smoeker wrote: > hola, > > the internal OM User gets created based on the data retrieved via LDAP > Lookup (in case of succesful login). > > please show us more of the logfile to identify a possible reason for > the nullpointer > > Dependent on the LdapServer u r using, the Fieldnames for the userdata > detail search have to differ. Within Code, the following LdapFields > are mapped : > > public static final String LDAP_KEY_LASTNAME = "sn"; > public static final String LDAP_KEY_FIRSTNAME = "givenName"; > public static final String LDAP_KEY_MAIL = "mail"; > public static final String LDAP_KEY_STREET = "streetAddress"; > public static final String LDAP_KEY_ADDITIONAL_NAME = "description"; > public static final String LDAP_KEY_FAX = > "facsimileTelephoneNumber"; > public static final String LDAP_KEY_ZIP = "postalCode"; > public static final String LDAP_KEY_COUNTRY = "co"; > public static final String LDAP_KEY_TOWN = "l"; > public static final String LDAP_KEY_PHONE = "telephoneNumber"; > > these values work fine for Active Directory e.g. - but for openLdap > the Detail Field names can differ > > -> so it could be possible, that u dont retrieve certaiin values > needed to create a local user. > -> the function createUserFromLdapData checks most of missing values > and replaces it by default values, but it still could be possible, > that an error occurs. > -> if u want to debug that, u could sysout the userdata within that > function and check, if some values are emtpy and if they are requiered > for creating a user object (nullable column?) > > see ya > > Smoeker > > see ya > > On 8 Jan., 13:41, maillist sev wrote: > > > > > Hello there, > > > today I've successfully configured the LDAP for openmeetings. The > > first two or three users where successfully created in openmeetings. > > But after that (or with a new browser-session on another PC) no new > > user was created. > > When a user want to log in, everything works fine --> means: > > Openmeetings checks if he entered the corrected Login-Information > > But after that, no User is created and the following error is shown in > > the log...: > > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > > Working Userdata : null > > > I've looked in the code, and this means, the user can't be created. > > But why? > > > Thanks for your help. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
Re: Error on Working Userdata
hola, the internal OM User gets created based on the data retrieved via LDAP Lookup (in case of succesful login). please show us more of the logfile to identify a possible reason for the nullpointer Dependent on the LdapServer u r using, the Fieldnames for the userdata detail search have to differ. Within Code, the following LdapFields are mapped : public static final String LDAP_KEY_LASTNAME = "sn"; public static final String LDAP_KEY_FIRSTNAME = "givenName"; public static final String LDAP_KEY_MAIL = "mail"; public static final String LDAP_KEY_STREET = "streetAddress"; public static final String LDAP_KEY_ADDITIONAL_NAME = "description"; public static final String LDAP_KEY_FAX = "facsimileTelephoneNumber"; public static final String LDAP_KEY_ZIP = "postalCode"; public static final String LDAP_KEY_COUNTRY = "co"; public static final String LDAP_KEY_TOWN = "l"; public static final String LDAP_KEY_PHONE = "telephoneNumber"; these values work fine for Active Directory e.g. - but for openLdap the Detail Field names can differ -> so it could be possible, that u dont retrieve certaiin values needed to create a local user. -> the function createUserFromLdapData checks most of missing values and replaces it by default values, but it still could be possible, that an error occurs. -> if u want to debug that, u could sysout the userdata within that function and check, if some values are emtpy and if they are requiered for creating a user object (nullable column?) see ya Smoeker see ya On 8 Jan., 13:41, maillist sev wrote: > Hello there, > > today I've successfully configured the LDAP for openmeetings. The > first two or three users where successfully created in openmeetings. > But after that (or with a new browser-session on another PC) no new > user was created. > When a user want to log in, everything works fine --> means: > Openmeetings checks if he entered the corrected Login-Information > But after that, no User is created and the following error is shown in > the log...: > [NioProcessor-4] ERROR o.o.app.data.user.Usermanagement - Error on > Working Userdata : null > > I've looked in the code, and this means, the user can't be created. > But why? > > Thanks for your help. -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
