https://bugs.freedesktop.org/show_bug.cgi?id=84190

          Priority: medium
            Bug ID: 84190
          Assignee: [email protected]
           Summary: libcmis: Wrong Password Entered For Alfresco Never
                    Allows For Correction
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: [email protected]
          Hardware: Other
            Status: UNCONFIRMED
           Version: 4.4.0.0.alpha0+ Master
         Component: framework
           Product: LibreOffice

There are two places where if a wrong password is entered when connecting to
Alfresco using libcmis that you cannot make a correct easily and this causes
problems with user experience.

Root cause of this failure is that LO retains your entered account/password for
the current session -- even if it's wrong.

1) When you first are making a connection to Alfresco, you are prompted for
your account name and password in order to find the "Main Repository".  This
happens when you hit the refresh symbol and are prompted for your
account/password.  If you enter the wrong combination it silently fails and the
user is never given notice of failure nor given a way to fix it.  Work around
is to completely close LO and re-open and attempt it again.  

2) If you have the Alfresco connection created as a shortcut, and enter the
wrong account or password, you get a dialog about a general IO error with no
indication of why it's failing.  The wrong account or password is held in
memory until you close and reopen LO.

Proper fix would be for libcmis to report authentication failure and create a
dialog to alert user, and then give the user chances to re-enter.

This is broken in LO 4.2.X and also in 4.4 (master).  Requesting please fix and
backport to previous versions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to