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

Login popup is shown when using digest auth despite creating client with proper user data #235

Open
Freir96 opened this issue Jan 14, 2021 · 4 comments

Comments

@Freir96
Copy link

Freir96 commented Jan 14, 2021

I changed the digest option in my client to true, but instead of using the proper login and password I am asked to log in by a popup window showing up when I make any request using WebDAV. After using the same username and password as when I create the client it works fine, but can I disable this popup somehow?

@perry-mitchell
Copy link
Owner

@Freir96 There's most likely something wrong with the authentication being made.. Any chance you can record the headers when making this request? It'd be important to see what's being sent by the client and what's being received. Just make sure to strip/obfuscate any auth hashes or passwords.

@Freir96
Copy link
Author

Freir96 commented Jan 15, 2021

@perry-mitchell Those are the headers after I refused to fill in the login data on the popup window.
Request:

Accept: text/plain
Accept-Encoding: gzip, deflate, br
Accept-Language: pl-PL,pl;q=0.9
Connection: keep-alive
Depth: 1
Host: localhost:4200
Origin: http://localhost:4200
Referer: http://localhost:4200/auth/login
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin

Response:

access-control-allow-credentials: true
access-control-allow-origin: *
access-control-expose-headers: DAV, content-length, Allow
allow: OPTIONS,MKCOL,LOCK,POST,PUT
connection: close
content-length: 0
date: Fri, 15 Jan 2021 11:43:39 GMT
dav: 1,2
ms-author-via: DAV
server: webdav-server/2.6.2
www-authenticate: Digest realm="Default realm", qop="auth", nonce="", opaque=""
X-Powered-By: Express

I should probably also mention that I am using proxy to avoid the cors error.

@perry-mitchell
Copy link
Owner

If you're still working around this error, can you please include your code for review? Obviously after having removed any credentials (please leave the structure the same, however).

@Freir96
Copy link
Author

Freir96 commented Mar 28, 2021

We are currently making some changes in the back-end, that could solve our problem. I will inform you once I learn anything new.

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

No branches or pull requests

2 participants