Bug 186150 - Freebusy authorization problem with Kolab Stable 2.2.0
Summary: Freebusy authorization problem with Kolab Stable 2.2.0
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 20:32 UTC by Gregor A.
Modified: 2017-01-07 21:42 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
User Password (286.51 KB, image/png)
2009-03-06 19:01 UTC, Gregor A.
Details
Here is the file download, with Konqueror (454 bytes, application/octet-stream)
2009-03-12 18:58 UTC, Gregor A.
Details
Here is the new File. (386 bytes, application/octet-stream)
2009-03-13 19:51 UTC, Gregor A.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor A. 2009-03-04 20:32:44 UTC
Version:           4.2.1 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Since version 2.2.1 it is not possible to load the Freebusy informations from Kolab server.
I become a USER / Passwort question if I tray it.

But the Freebusy don't work after enter the right values.

A direct https test connection from the browser works perfectly.

The version of kdepim 2.2.0 dont't have this problem.
The problem exist since an upgrade from KDE + KDEPIM 2.2.0 to 2.2.1.
Comment 1 Bernhard E. Reiter 2009-03-06 10:03:58 UTC
Do you have access to the Kolab Server? If so, it would be interesting to see the https request the client (Kontact) is sending. Ideally you can compare it to the request you've got from a working version.
Comment 2 Bernhard E. Reiter 2009-03-06 10:07:16 UTC
And another question, you are reporting this as a problem of Kontact
or of the Kolab Server? Because there is no 2.2.1 Kolab Server - yet.
The current version is 2.2.1-rc1 and was released yesterday. Were you using this or the the 2.2.1-beta1?

(Stable version of Kolab Server ist 2.2.0 as of writing.) If there is a defect in the Kolab Server, please report on kolab-devel@ or kolab-users@.
Especially when in the beta1 or the rc1. We appreciate it. :)
Comment 3 Gregor A. 2009-03-06 19:01:21 UTC
Created attachment 31849 [details]
User Password
Comment 4 Gregor A. 2009-03-06 19:14:44 UTC
Please see my attachment...
I use the actual KDE 4.2.1 from Debian Experimental together with the stable Kolab 2.2.0.

The first time after login Kontact shows me this dialog.

But after enter the values, I can not see the freebusy informations.

I report this as a problem of Kontact.
The previous version 2.2.0 has no problems with freebusy, I have tested it.

I have only three packages not updated to version 2.2.1:
kdebase-workspace
kdebase-workspace-bin
kdebase-workspace-data

This packages are actually not in experimental.
This packages are actually version 2.2.0 on system.  

After the last Update Kontact asks me to accept the SERVER SSL Certificate again.

This Certificate was already accepted.

Maybe this is problem ???
Comment 5 Gregor A. 2009-03-08 16:51:33 UTC
Hi, now is my system complete on version 2.2.1.
KDE and KDE PIM are the newest Debian Experimental.

The problem stays...

Kontact Freebusy don't work anymore together with Kolab...
Comment 6 Bernhard E. Reiter 2009-03-09 09:32:34 UTC
Gregor,
what does your "kontact --version" say?
Do you have access to the Kolab Server? If yes, can you check the apache log
during Freebusy queries?

Are you in a position to try the http://websvn.kde.org/branches/kdepim/enterprise4/ branch?
Comment 7 Bernhard E. Reiter 2009-03-09 09:34:52 UTC
An additional question: How are the other passwords entered or saved for kontact? Using kwallet?
Comment 8 Gregor A. 2009-03-09 17:43:10 UTC
Hello,

kontact --version
Qt: 4.4.3
KDE: 4.2.1 (KDE 4.2.1)
Kontact: 1.4.1

kwallet is deactivated
Comment 9 Allen Winter 2009-03-11 11:45:29 UTC
Till, Bernhard,

I wonder if this could have anything to do with the FreeBusyCheckHostname setting in korganizer.kcfg?  Remember this undocumented, hidden config option? I changed the default from 'true' to 'false' in trunk, not 4.2.1.  So this shouldn't have any affect if Gregor is using 4.2.1.

... just trying to recall anything that may have changed in KOrganizer recently...
Comment 10 Bernhard E. Reiter 2009-03-11 13:03:54 UTC
I is very unlikely to have to do with FreeBusyCheckHostname,
as the new default makes more cases work. 
I am still waiting for Gregor to answer the server question. :)
If anybody else has a test setting with a similiar version to test with,
this might be useful as well.
Comment 11 Gregor A. 2009-03-11 19:52:44 UTC
Hello, 
Yes I have access to the Kolab Server, I will check the logs and post it here.

Yesterday I have updatet my Kolab Server to the newest: RC1 2.2.1.

The Kontact Freebusy problem stays, free busy in horde works perfectly.
 
To the kdepim branch:
I have never build so big packages.
Build instructions are very helpful for me, so I can test it on my weekend.
Comment 12 Gregor A. 2009-03-11 20:02:42 UTC
Here the logs after the free busy access:
tail /kolab/var/apache/log/apache-access.log
station-ea.netkult.eu - - [11/Mar/2009:19:55:51 +0100] "GET /freebusy/e.adamczyk@netkult.eu.ifb HTTP/1.1" 401 401
station-ea.netkult.eu - g.adamczyk@netkult.eu [11/Mar/2009:19:56:02 +0100] "GET /freebusy/e.adamczyk@netkult.eu.ifb HTTP/1.1" 200 454

tail /kolab/var/kolab-freebusy/log/freebusy.log
Mar 11 00:49:22 Kolab Free/Busy [debug] [horde] Free/busy generation complete. [on line 174 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 00:50:45 Kolab Free/Busy [debug] [horde] Starting generation of free/busy data for user g.adamczyk@netkult.eu [on line 190 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 00:50:46 Kolab Free/Busy [debug] [horde] Free/busy data of owner g.adamczyk@netkult.eu on server https://mail.netkult.eu/freebusy requested by user e.adamczyk@netkult.eu. [on line 203 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 00:50:46 Kolab Free/Busy [debug] [horde] Extended attributes on folder  disallowed for user e.adamczyk@netkult.eu. [on line 375 of "/kolab/lib/php/Horde/Kolab/FreeBusy/Cache.php"]
Mar 11 00:50:46 Kolab Free/Busy [debug] [horde] Delivering complete free/busy data. [on line 224 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 00:50:46 Kolab Free/Busy [debug] [horde] Free/busy generation complete. [on line 231 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 19:56:02 Kolab Free/Busy [debug] [horde] Starting generation of free/busy data for user e.adamczyk@netkult.eu [on line 190 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 19:56:02 Kolab Free/Busy [debug] [horde] Free/busy data of owner e.adamczyk@netkult.eu on server https://mail.netkult.eu/freebusy requested by user g.adamczyk@netkult.eu. [on line 203 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 19:56:02 Kolab Free/Busy [debug] [horde] Delivering complete free/busy data. [on line 224 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]
Mar 11 19:56:02 Kolab Free/Busy [debug] [horde] Free/busy generation complete. [on line 231 of "/kolab/lib/php/Horde/Kolab/FreeBusy.php"]

station-server:~# ls -al /kolab/var/apache/log/
insgesamt 8928
drwxr-xr-x 5 kolab   kolab      4096 11. Mär 00:34 .
drwxr-xr-x 4 kolab   kolab      4096  4. Mär 12:56 ..
-rw-r--r-- 1 root    root    8646708 11. Mär 19:56 apache-access.log
-rw-r--r-- 1 root    root     439186 11. Mär 18:32 apache-error.log
drwxr-xr-x 2 kolab-n kolab-n    4096 21. Feb 10:46 fbview
drwxr-xr-x 2 kolab-n kolab-n    4096 26. Okt 19:48 horde
drwxr-xr-x 2 kolab-n kolab-n    4096  4. Mär 12:56 php
-rw-r--r-- 1 kolab-n root       4096 11. Mär 00:49 ssl_scache.dir
-rw-r--r-- 1 kolab-n root       3072 11. Mär 19:55 ssl_scache.pag
Comment 13 Bernhard E. Reiter 2009-03-12 10:07:35 UTC
This seems to be a successfull get request, though a bit short:

| station-ea.netkult.eu - g.adamczyk@netkult.eu [11/Mar/2009:19:56:02 +0100] "GET
/freebusy/e.adamczyk@netkult.eu.ifb HTTP/1.1" 200 454

So if konqueror also get this file for good, it might be a defect of Kontact displaying the freebusy list. I guess Allen will need to try to reproduce.

Gregor, can you send the file you get with konqueror from that url
and decribe what you can see in the freebusy list for this user in Kontact?
Comment 14 Gregor A. 2009-03-12 18:58:16 UTC
Created attachment 32059 [details]
Here is the file download, with Konqueror
Comment 15 Bernhard E. Reiter 2009-03-13 12:49:11 UTC
(http://bugs.kde.org/attachment.cgi?id=32059) is an empty Freebusy list.
You should see free space in your kontact if you add this person to the attendee list.

If there should be entries in there, try to make a new entry in a calender
which is freebusy relevant with Kontact, sync and check if the trigger link wen through.
Comment 16 Gregor A. 2009-03-13 19:51:11 UTC
Created attachment 32076 [details]
Here is the new File.
Comment 17 Gregor A. 2009-03-13 19:56:48 UTC
I have still the same problem, still the same user / password dialog and no free busy information in kontact.

I uploaded the new freebusy File:
https://bugs.kde.org/attachment.cgi?id=32076

The calendar entry is created with horde.
Comment 18 Bernhard E. Reiter 2009-03-16 08:46:46 UTC
Kontact should display the one appointment in the file, so it looks 
like a defect. (Assuming you did establish that Kontact also successfully 
retrieves this particular file.)

Allen, maybe you can make your Kontact trying to display the file
which would exclude that it is the file contents that KOrganizer cannot parse,
if you like to help Gregor, otherwise you probably know better than me what 
to do next to diagnose the Kontact problem.
Comment 19 Denis Kurz 2016-09-24 19:30:59 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 20 Denis Kurz 2017-01-07 21:42:40 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.