Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Credentials not accepted #457

Closed
Gabbalo opened this issue Feb 17, 2016 · 3 comments
Closed

Credentials not accepted #457

Gabbalo opened this issue Feb 17, 2016 · 3 comments
Assignees
Labels

Comments

@Gabbalo
Copy link

Gabbalo commented Feb 17, 2016

Hi there,
I installed Baikal an it runs as far as I can tell properly.
But when I try to access the default addressbook for user-a at address
https://fancydomain.tld/card.php/addressbooks/user-a/default
the credentials are always wrong.
I tried to reset the password, typed it via PasswordManager and copy/paste ... nothing works.

Error-Message:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:sabredav-version>3.1.1/s:sabredav-version
<s:exception>Sabre\DAV\Exception\NotAuthenticated/s:exception
<s:message>Username or password was incorrect/s:message
/d:error

@nowotny
Copy link

nowotny commented Feb 18, 2016

That's because it tries to authenticate against 'SabreDAV' realm instead of 'BaikalDAV' as it's set in the default config.

The workaround for now is to go to the admin panel and in 'System setting' change the 'Auth realm' to 'SabreDAV'.

@evert evert added the bug label Feb 19, 2016
@evert evert self-assigned this Feb 19, 2016
@evert evert closed this as completed in c75df3a Feb 19, 2016
@Gabbalo
Copy link
Author

Gabbalo commented Feb 19, 2016

Been there, done that ... now even my admin password for admin-panel is rejected.
Probably that was not the solution :(

@evert
Copy link
Member

evert commented Feb 19, 2016

There was a problem with Digest auth, which I've now fixed and released in 0.3.3. As a temporary workaround you may try switching to Basic auth.

However, changing the realm manually probably just makes things worse, unless you also re-generate the passwords.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants