6.0.0-alpha12
6/12/25

[#12300] Problem with authentication of CalDAV Server
Summary Problem with authentication of CalDAV Server
Queue Synchronization
Queue Version Git master
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester Twilek (at) gmx (dot) de
Created 06/04/2013 (4391 days ago)
Due
Updated 08/27/2013 (4307 days ago)
Assigned 06/05/2013 (4390 days ago)
Resolved 08/27/2013 (4307 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/27/2013 10:33:02 AM Jan Schneider State ⇒ No Feedback
 
07/12/2013 06:42:54 AM Ralf Lang Comment #8 Reply to this comment
I also don't know what  "in IMP allow user listing?" means
I found no option in imp config
Take a look at imp/config/backends.php too.
06/06/2013 12:56:07 PM as (at) schneider-pc (dot) ch Comment #7 Reply to this comment
I also don't know what  "in IMP allow user listing?" means
I found no option in imp config

06/05/2013 09:25:33 PM as (at) schneider-pc (dot) ch Comment #6 Reply to this comment
I have the same problem .. backend Auth is also IMP

there is a patch on http://bugs.horde.org/ticket/12307
but it doesn't seem to work
after patch no error if i open it over the browser ... but dav is emtpy
06/05/2013 02:13:07 PM Twilek (at) gmx (dot) de Comment #5 Reply to this comment
I have checked the backends.php and the imp configuration page and 
havenĀ“t found any settings for user listing. My backends.php for the 
server looks like this:

$servers['imap'] = array(
     // ENABLED by default; will connect to IMAP port on local server
     'disabled' => false,
     'name' => 'IMAP Server',
     'hostspec' => 'localhost',
     'hordeauth' => false,
     'protocol' => 'imap',
     'port' => 143,
     // Plaintext logins are disabled by default on IMAP servers (see RFC 3501
     // [6.2.3]), so TLS is the only guaranteed authentication available by
     // default.
     'secure' => 'tls',
  'spam' => array(
          'innocent' => array(
              'display' => true,

              // Email reporting driver
              'email' => null,
              'email_format' => 'digest',

              // Null reporting driver
              'null' => true,

              // Program reporting driver
              'program' => '/usr/bin/spamassassin -k'
          ),
          'spam' => array(
              'display' => false,

              // Email reporting driver
              'email' => null,
              'email_format' => 'digest',

              // Null reporting driver
              'null' => true,

              // Program reporting driver
              'program' => '/usr/bin/spamassassin -r'

          ),
         // // It is possible to directly define additional spam drivers.
         // // The 'drivers' array should contain a list of driver objects
         // // (these classes must implement the IMP_Spam_Base class).
         // 'drivers' => array(
         //     new IMP_Example_Spam_Driver()
         // )
     ),
);
I use Dovecot 1.3 with the IMAP protocol.
Cannot reproduce. Does your IMP backend allow user listing?
That's not the answer to my question. Maybe I should have been more 
specific: does your backend *configuration* in IMP allow user listing?
06/05/2013 01:49:02 PM Jan Schneider Comment #4 Reply to this comment
I use Dovecot 1.3 with the IMAP protocol.
Cannot reproduce. Does your IMP backend allow user listing?
That's not the answer to my question. Maybe I should have been more 
specific: does your backend *configuration* in IMP allow user listing?
06/05/2013 01:35:53 PM Twilek (at) gmx (dot) de Comment #3 Reply to this comment
I use Dovecot 1.3 with the IMAP protocol.
Cannot reproduce. Does your IMP backend allow user listing?
06/05/2013 10:21:33 AM Jan Schneider Summary ⇒ Problem with authentication of CalDAV Server
 
06/05/2013 10:19:26 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Cannot reproduce. Does your IMP backend allow user listing?
06/04/2013 11:20:00 PM Twilek (at) gmx (dot) de Comment #1
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Synchronization
Summary ⇒ Porblem with authentication of Caldav Server
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
Since updating to Webmail 5.1.0 when I try to open the Caldav Account 
Link provided by kronolith like 
https://www.xxx.de/webmail/rpc/principals/username/ I get a html 
Credentials request. When entering the right credentials I get a
<d:error><s:exception>Sabre\DAV\Exception\NotFound</s:exception><s:message>User username does not 
exist</s:message><s:sabredav-version>1.8.4</s:sabredav-version></d:error>

althought the user "username" exists. I do the authentication via IMP. 
This error did not appear with the beta packages.

Saved Queries