[CalendarServer-dev] [Calendar and Contacts Server] #422: Digest authentication algorithm md5 & RFC2617

[Calendar and Contacts Server]

#422: Digest authentication algorithm md5 & RFC2617
-----------------------------------------+----------------------------------
 Reporter:  marten.gajda@…               |       Owner:  cdaboo@…          
     Type:  Defect                       |      Status:  new               
 Priority:  2: Expected                  |   Milestone:  CalendarServer-3.x
Component:  Calendar Server              |    Severity:  Other             
 Keywords:  Digest authentication md5    |       Radar:                    
-----------------------------------------+----------------------------------
Changes (by wsanchez@…):

  * priority:  5: Not set => 2: Expected
  * owner:  wsanchez@… => cdaboo@…
  * milestone:  => CalendarServer-3.x


Old description:

> I'm writing a CardDAV-Sync adapter for Android and came across the
> following issue when connecting to caldavd:
> Android's HTTP implementation can not handle digest authentication when
> algorithm is set to "md5" instead of "MD5".
>
> I do not know whether Android is wrong or caldavd.
> RFC2617 states:
>
> algorithm = "algorithm" "=" ( "MD5" | "MD5-sess" | token )
>
> but does not say anything about case-sensitivity.
>
> I'd like to know your opinion about this. I'm not sure if I can work
> around this issue somehow. For the moment my only solution is to advise
> my users to change the algorithm to MD5.
>
> Thanks
>
> Marten

New description:

 I'm writing a CardDAV-Sync adapter for Android and came across the
 following issue when connecting to caldavd:
 Android's HTTP implementation can not handle digest authentication when
 algorithm is set to "md5" instead of "MD5".

 I do not know whether Android is wrong or caldavd.
 RFC2617 states:

 {{{
 algorithm = "algorithm" "=" ( "MD5" | "MD5-sess" | token )
 }}}
 but does not say anything about case-sensitivity.

 I'd like to know your opinion about this. I'm not sure if I can work
 around this issue somehow. For the moment my only solution is to advise my
 users to change the algorithm to MD5.

 Thanks

 Marten

--

-- 
Ticket URL: <http://trac.calendarserver.org/ticket/422#comment:1>
Calendar and Contacts Server </>
HTTP/WebDAV/CalDAV Server