Announcement

Collapse
No announcement yet.

Trouble with password changing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Trouble with password changing

    Hello,
    I've finally managed to install open exchange on my debian box and everything works fine. The setup is:
    - Open Xchange OSE
    - Exim
    - Cyrus 2.2
    - Authentication via PAM / MYSQL against the ox database
    - SSL / TLS-Encryption on all levels.

    But: One rather simple thing doesn't work: Password changing.

    I can perfectly log into the system, use it, receive and send emails via OX. But if I try to change the password I receive to following error message:

    "Fehlermeldung: Ungültige Authorisierungsdaten (LGI-0006, 1906046267-433)"

    Any ideas?

    Yt,

    Gunnar

  • #2
    Hi Gunnar,

    could you please post the stacktrace which is written to the logfile when this issue occurs?

    Thanks

    Comment


    • #3
      Badly enough there is no such thing as a stacktrace in any of the logfiles files. They remain strangely quiet.

      Looks like logging is completely turned off. What magic do I have to invoke to enable logging?

      Yt,

      Gunnar

      Comment


      • #4

        Comment


        • #5
          Thanks, that did the trick. Didn't know about the remot debugging, although I use debian for a decade or so now.

          The exception you asked for is:

          Code:
          Apr  7 19:33:38 localhost 2009-04-07 19:33:38,231 open-xchange-groupware ERROR [com.openexchange.passwordchange.servlet.PasswordChangeServlet][AJPListener-00007]: com.openexchange.passwordchange.servlet.PasswordChangeServlet,actionPutUpdate LGI-0006 Category=1 Message=Invalid credentials. exceptionID=-1818787818-111 
          Apr  7 19:33:38 localhost LGI-0006 Category=1 Message=Invalid credentials. exceptionID=-1818787818-111
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.PasswordChangeService.check(PasswordChangeService.java:157)
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.PasswordChangeService.perform(PasswordChangeService.java:101)
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.servlet.PasswordChangeServlet.actionPutUpdate(PasswordChangeServlet.java:203)
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.servlet.PasswordChangeServlet.actionPut(PasswordChangeServlet.java:165)
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.servlet.PasswordChangeServlet.doPut(PasswordChangeServlet.java:129)
          Apr  7 19:33:38 localhost     at javax.servlet.http.HttpServlet.service(HttpServlet.java:619)
          Apr  7 19:33:38 localhost     at com.openexchange.ajax.AJAXServlet.service(AJAXServlet.java:380)
          Apr  7 19:33:38 localhost     at com.openexchange.ajax.SessionServlet.service(SessionServlet.java:152)
          Apr  7 19:33:38 localhost     at com.openexchange.ajax.PermissionServlet.service(PermissionServlet.java:98)
          Apr  7 19:33:38 localhost     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
          Apr  7 19:33:38 localhost     at com.openexchange.ajp13.AJPv13RequestHandler.doServletService(AJPv13RequestHandler.java:575)
          Apr  7 19:33:38 localhost     at com.openexchange.ajp13.AJPv13Request.response(AJPv13Request.java:108)
          Apr  7 19:33:38 localhost     at com.openexchange.ajp13.AJPv13RequestHandler.createResponse(AJPv13RequestHandler.java:385)
          Apr  7 19:33:38 localhost     at com.openexchange.ajp13.AJPv13Connection.createResponse(AJPv13Connection.java:192)
          Apr  7 19:33:38 localhost     at com.openexchange.ajp13.AJPv13Listener.run(AJPv13Listener.java:245)
          Apr  7 19:33:38 localhost     at java.lang.Thread.run(Thread.java:595)
          Apr  7 19:33:38 localhost     aused by: LGI-0006 Category=1 Message=Invalid credentials. exceptionID=-1818787818-110
          Apr  7 19:33:38 localhost     at com.openexchange.authentication.exception.LoginExceptionFactory.createException(LoginExceptionFactory.java:82)
          Apr  7 19:33:38 localhost     at com.openexchange.authentication.exception.LoginExceptionFactory.createException(LoginExceptionFactory.java:62)
          Apr  7 19:33:38 localhost     at com.openexchange.exceptions.Exceptions.create(Exceptions.java:128)
          Apr  7 19:33:38 localhost     at com.openexchange.exceptions.Exceptions.create(Exceptions.java:132)
          Apr  7 19:33:38 localhost     at com.openexchange.exceptions.Exceptions.create(Exceptions.java:144)
          Apr  7 19:33:38 localhost     at com.openexchange.authentication.LoginExceptionCodes.create(LoginExceptionCodes.java:175)
          Apr  7 19:33:38 localhost     at com.openexchange.authentication.database.impl.DatabaseAuthentication.handleLoginInfo(DatabaseAuthentication.java:99)
          Apr  7 19:33:38 localhost     at com.openexchange.passwordchange.PasswordChangeService.check(PasswordChangeService.java:152)
          Apr  7 19:33:38 localhost     ... 15 more
          This problem currently affects all users of this open-xchange instance.

          Yt,

          Gunnar
          Last edited by Guest; 04-07-2009, 07:34 PM.

          Comment


          • #6
            Thats really strange... mhh could you try to monitor the network traffic and check what data is supplied when calling the plugin?

            Comment


            • #7
              Ok, found a way to analyse the network traffic via wireshark.

              The tcp stream I've captured reads:

              Code:
              .4......HTTP/1.1.../ajax/passwordchange...87.240.239.131.....www.gridcon.de..........www.gridcon.de....bMozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.7) Gecko/2009030814 Iceweasel/3.0.7 (Debian-3.0.7-1)....?text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8....#de-de,de;q=0.8,en-us;q=0.5,en;q=0.3.....gzip,deflate.....ISO-8859-1,utf-8;q=0.7,*;q=0.7..
              Keep-Alive...300....
              keep-alive.....text/javascript; charset=UTF-8..
              ."https://www.gridcon.de/ox6/ox.html.....88.....JSESSIONID=46068c89214b4d10889306f82f0da944.APP1; open-xchange-session-ab2895d444424684a22445f30b0798f0=2a451a9b8dda42cb9ebb71fb7d0aea2b...6action=update&session=ab2895d444424684a22445f30b0798f0...
              AES256-SHA......4.Z.X{"old_password":"<removed old pw>","new_password":"<removed new pw>","new_password2":"<removed new pw>"}
              Note that I removed the passwords manually due to obvious reasons but I've checked that they were ok.

              Yt,

              Gunnar

              Comment


              • #8
                Ok,
                I think I know what the problem is.

                When I initialized the context (createcontext) I forgot to tell the context that it is the default context.

                And I wondered, why people were not able to login. Finally found out about it when I traced the mysql.log. OX looks for an entry in the login2context-table "WHERE login_info='defaultcontext'".

                So I manually changed this field to "defaultcontext" and voila, login worked.

                Now I run into a different problem with this because the mysql query when trying to change the password is (traced via wireshark, hence the strange format):
                Code:
                SELECT login_info FROM login2context WHERE cid=1.....L....def.configdb
                login2context
                login2context
                login_info
                login_info.........P.................defaultcontext.........3....SELECT cid FROM login2context WHERE login_info='1'.....>....def.configdb
                OX looks for a row with "WHERE login_info='1'". Since I changed the login_info to "defaultcontext" this no longer contains the "1".

                Can you tell me what to do to fix this? One solution might be to create an other entry in the login2context with exactly this entry. But I do not know if this might cause trouble in different side of town.

                Yt,

                Gunnar

                Comment


                • #9
                  Ok,
                  implemented it this way. I've created a new entry in login2context with the values '1' for cid and '1' for login_info.

                  Login and password-change now both work.

                  But: Does this might have any strange side-effects?

                  Yt,

                  Gunnar

                  Comment

                  Working...
                  X