On Fri, 2009-09-25 at 19:04 +0200, Patrick Ohly wrote:
I'm getting the first message exchange done, now it fails with in
my
HTTP server script because I'm not handling the session ID yet (need to
follow the hints in your other email).
I've got the session handling more or less working, now I fail to get
the client authenticated in the server.
If I use
<requestedauth>md5</requestedauth>
<requiredauth>md5</requiredauth>
<autononce>yes</autononce>
<simpleauthuser>test</simpleauthuser>
<simpleauthpw>test</simpleauthpw>
then the server always replies with a challenge. I checked my client, it
has test/test as username/password. The client tries a few times to send
the right credentials, but eventually seems to give up. This did not
result in a failed sync status.
If I use
<requestedauth>none</requestedauth>
<requiredauth>none</requiredauth>
<autononce>yes</autononce>
<simpleauthuser>test</simpleauthuser>
<simpleauthpw>test</simpleauthpw>
then the server still rejects the first client's message with a 401
status, but sends no challenge and the client gives up immediately.
Where do I have to look in the server to debug the authentication
problem? I use SDK_textdb:
<plugin_module>[SDK_textdb]</plugin_module>
<plugin_sessionauth>yes</plugin_sessionauth>
<plugin_deviceadmin>yes</plugin_deviceadmin>
Hmm, I don't see where the SDK_textdb writes its files. I could of
course apply strace, but it is late again, so let me better ask. How do
I configure this? I saw something about it writing in the "application
datadir", but how do I change that? <binfilespath> is not accepted in a
server config.
This could be the problem; without storing the next nonce,
authentication will always fail.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.