http://bugs.meego.com/show_bug.cgi?id=1349
Summary: HTTP AUTH
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: ASSIGNED
Severity: normal
Priority: Low
Component: SyncML
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
This is from http://bugzilla.moblin.org/show_bug.cgi?id=2429
Description From pohly 2009-05-14 12:22:55 PST (-) [reply]
Copied from
https://sourceforge.net/tracker/?func=detail&aid=2056162&group_id=146288&atid=764733
Some SyncML servers require authentication via HTTP AUTH. I don't remember for
which server, but it was based on a user request.
Currently there are no setting for such HTTP AUTH credentials. Need to be added
(SyncEvolutionConfig.cpp) and hooked up with the HTTP transports (both libcurl
and libsoup).
------- Comment #1 From ruskie 2010-01-13 10:59:13 PST (-) [reply] -------
I have such a syncML server setup. In case there is need I can setup a
developer account to test this.
In my case it's reguralh http server with horde being http authed and being the
syncml server.
------- Comment #2 From pohly 2010-01-18 03:39:31 PST (-) [reply] -------
(In reply to comment #1)
> I have such a syncML server setup. In case there is need I can setup a
> developer account to test this.
Thanks for the offer. But I think we can test this more easily by extending our
own syncevo-http-server.py to offer HTTP AUTH as an optional feature.
> In my case it's reguralh http server with horde being http authed and being
> the
> syncml server.
Do you know whether the Horde server still requires a valid username/password
at the SyncML level? Is it the same as the HTTP AUTH password?
I am asking because the sync-UI would only be able to set one username/password
pair, the one for SyncML. We could add separate http-username/passsword
properties and define them so that setting them is only necessary when they
differ from the normal SyncML credentials. If unset and the HTTP server ask for
authorization, the SyncML credentials could be used.
------- Comment #3 From ruskie 2010-01-18 03:58:25 PST (-) [reply] -------
(In reply to comment #2)
> > In my case it's reguralh http server with horde being http authed and being
> > the
> > syncml server.
>
> Do you know whether the Horde server still requires a valid username/password
> at the SyncML level? Is it the same as the HTTP AUTH password?
It only requires the HTTP AUTH password. That's how it's configured. You can
configure it in so many different ways. But most usually use their own login
interface and the syncml layer requests the auth itself.
But with HTTP AUTH it only checks if you are authed and if you are it will
fulfill the request.
> I am asking because the sync-UI would only be able to set one
> username/password
> pair, the one for SyncML. We could add separate http-username/passsword
> properties and define them so that setting them is only necessary when they
> differ from the normal SyncML credentials. If unset and the HTTP server ask
> for
> authorization, the SyncML credentials could be used.
curl -k https://my.domain.tld/rpc.php
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
<head>
<title>401 - Unauthorized</title>
</head>
<body>
<h1>401 - Unauthorized</h1>
</body>
</html>
curl --user 'username:password' -k https://my.domain.tld/rpc.php
<?xml version="1.0"?><disco:discovery
xmlns:disco="http://schemas.xmlsoap.org/disco/";
xmlns:scl="http://schemas.xmlsoap.org/disco/scl/";>
<scl:contractRef ref="https://my.domain.tld/rpc.php?wsdl"; />
</disco:discovery>
Hope that helps.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
