You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "David Shapirovskiy (JIRA)" <ji...@apache.org> on 2012/10/29 10:21:13 UTC
[jira] [Updated] (OPENMEETINGS-452) LDAP issue. Cannot relogin with
user that already was logined before and then logged out
[ https://issues.apache.org/jira/browse/OPENMEETINGS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Shapirovskiy updated OPENMEETINGS-452:
--------------------------------------------
Fix Version/s: 2.0 Apache Incubator Release
> LDAP issue. Cannot relogin with user that already was logined before and then logged out
> ----------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-452
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-452
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.1 Apache Incubator Release
> Environment: Centos 6.3 i386
> Reporter: David Shapirovskiy
> Assignee: SebastianWagner
> Labels: LDAP, Openmeetings
> Fix For: 2.0 Apache Incubator Release
>
>
> Using the latest build (on 24 10 2012). Using LDAP authentification. First time logging user is normal and he is automatically arranged to default Usergroup. But when i logout and then try to login with the same user creditionals i receive an error (Unknown error code -1).
> In openmeetings.log i see error message that it is unable to refresh session
> this is the part of logfile about login problem
> Authentification to LDAP - Server start
> DEBUG 10-24 04:19:07.533 LdapAuthBase.java 990260 151 org.apache.openmeetings.ldap.LdapAuthBase [NioProcessor-5] - loginToLdapServer
> DEBUG 10-24 04:19:07.541 Usermanagement.java 990268 1530 org.apache.openmeetings.data.user.Usermanagement [NioProcessor-5] - Usermanagement.getUserByLogin : ShapirovskiyD@mskps.l$
> DEBUG 10-24 04:19:07.549 LdapLoginManagement.java 990276 537 org.apache.openmeetings.ldap.LdapLoginManagement [NioProcessor-5] - User already exists -> Update of current passwd
> DEBUG 10-24 04:19:07.550 Sessionmanagement.java 990277 175 org.apache.openmeetings.data.basic.Sessionmanagement [NioProcessor-5] - updateUser User: 7 || 3305bd1a5409260c721be16da$
> DEBUG 10-24 04:19:07.552 Sessionmanagement.java 990279 195 org.apache.openmeetings.data.basic.Sessionmanagement [NioProcessor-5] - Found session to update: 3305bd1a5409260c721be1$
> DEBUG 10-24 04:19:07.587 Usermanagement.java 990314 1614 org.apache.openmeetings.data.user.Usermanagement [NioProcessor-5] - Usermanagement.getUserByLogin
> DEBUG 10-24 04:19:07.588 ManageCryptStyle.java 990315 38 org.apache.openmeetings.utils.crypt.ManageCryptStyle [NioProcessor-5] - getInstanceOfCrypt: org.apache.openmeetings.utils$
> DEBUG 10-24 04:19:07.588 ManageCryptStyle.java 990315 43 org.apache.openmeetings.utils.crypt.ManageCryptStyle [NioProcessor-5] - configKeyCryptClassName: org.apache.openmeetings.$
> ERROR 10-24 04:19:07.588 LdapLoginManagement.java 990315 565 org.apache.openmeetings.ldap.LdapLoginManagement [NioProcessor-5] - Error updating user : null
> DEBUG 10-24 04:19:07.669 ErrorService.java 990396 60 org.apache.openmeetings.remote.ErrorService [NioProcessor-5] - errorid, language_id: -1|1
> DEBUG 10-24 04:19:07.672 ErrorService.java 990399 64 org.apache.openmeetings.remote.ErrorService [NioProcessor-5] - eValues.getFieldvalues_id() = 334
> So i meant - first login of user is perfect. But later logins are causing errors. Solution is to delete problem user in administration section so after that it would be his first login again.
> And this issue is only on LDAP login. LocalDB login is always perfect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira