Bug 295618 - dav groupware resource always asks about logging in on startup
Summary: dav groupware resource always asks about logging in on startup
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-09 14:57 UTC by Silver Salonen
Modified: 2017-01-07 22:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Silver Salonen 2012-03-09 14:57:04 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.21 (KHTML, like Gecko) Chrome/19.0.1046.0 Safari/535.21 SUSE/19.0.1046.0
Build Identifier: 

I've added DAV resource-based eGroupware calendar/TODO into KOrganizer.
There are both username and password inserted into the settings, but when I start KOrganizer, it always prompts: "You are about to log in to the site "egw.mydomain" with the username "silver", but the website does not require authentication. This may be an attempt to trick you. Is "egw.mydomain" the site you want to visit?"
I choose yes and everything is well.

Reproducible: Always

Steps to Reproduce:
1. Add eGroupware DAV resource into KOrganizer (Akonadi)
2. Start KOrganizer
Actual Results:  
Prompt: "You are about to log in to the site "egw.mydomain" with the username "silver", but the website does not require authentication. This may be an attempt to trick you. Is "egw.mydomain" the site you want to visit?"
And no possibility to set it to never be asked again.

Expected Results:  
Start without the (invalid?) prompt or at least make it possible to ignore it always from now on.
Comment 1 Grégory Oestreicher 2012-03-10 17:09:33 UTC
Hi,

Which KDE / KDE PIM versions are you using?

Cheers,
Grégory
Comment 2 Silver Salonen 2012-03-10 18:16:32 UTC
Started using DAV resource in KDE 4.8.0, currently using 4.8.1.
Comment 3 Grégory Oestreicher 2012-03-10 19:15:07 UTC
This means that the remote end answers with something else than a 401 (maybe a 3XX response code) that triggers this alert. If you try to connect to the address you configured with a web browser are you redirected to another page? If so, try to configured the URL at which you are.

Cheers,
Grégory
Comment 4 Silver Salonen 2012-03-12 10:00:04 UTC
Well, the eGroupware resource is configured with URL ".../groupdav.php/", but its calendar is under ".../groupdav.php/calendar/", so I guess some redirection takes place indeed?

I now tried changing protocol (CalDAV and CardDAV) URLs of the resource. When I set CalDAV URL to ".../groupdav.php/calendar/", I lost the TODO-list (which is under ".../groupdav.php/infolog/"), but the warning remained.

So I don't know the one and only answer to your question :)
Comment 5 Grégory Oestreicher 2012-03-12 10:06:30 UTC
For egw /groupdav.php/ is the standard location. I was more thinking about a redirection from, for example, https://egw.domain.com/groupdav.php/ to https://domain.com/egw/groupdav.php/.
Comment 6 Silver Salonen 2012-03-12 10:12:33 UTC
Ah, I see. But no, there's no redirection in that part.
Comment 7 Silver Salonen 2012-04-16 21:17:15 UTC
I've discovered that actually KOrganizer opens the calendar before I manage to hit "yes". I did not realize it before, because it takes about 5 seconds for the calendar to open, so I had already clicked "yes" when the calendar opened.

Anyway, maybe that question is not asked in order to decide whether to open the calendar, but for something else?
Comment 8 Denis Kurz 2016-09-24 20:31:20 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 9 Denis Kurz 2017-01-07 22:07:12 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.