Modify ↓
#9198 closed defect (wontfix)
Problems with Digest HTTP authentication
Reported by: | anonymous | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Component: | XmlRpcPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
Hello,
Will this ever be fixed? I have many users and switching to Basic HTTP authentication would be a long process.
Problems with Digest HTTP authentication The xmlrpclib.ServerProxy client - as demonstrated in the following examples - will not work with a Digest-based HTTP authentication: you need to set up a Basic HTTP authentication on server side to make the examples work. If you use the standalone Trac daemon, this means that you cannot use the tracd -a option (htdigest authentication file). Use trac --basic-auth (htpasswd authentication file) instead.
Attachments (0)
Note: See
TracTickets for help on using
tickets.
No, it won't be fixed. The reason is that it has nothing at all to do with the XmlRpcPlugin - it is purely restrictions in the CLIENT you are using (
xmlrpclib.ServerProxy
). That client, and many others, seems to be happy to settle for basic-auth only support. It's a shame, but that is beyond what I can influence.Feel free to make a custom client that communicates its XML or JSON to the server as it sees fit - it is for instance what we do in the Bitten project where we have a build slave that communicates with a Trac handler and it can handle Basic, Digest or even AccountManagerPlugin forms login with session handling. Bitten communicates using custom XML over HTTP, but the general idea would be the same for a custom RPC client.
See slave.py for example client code from the Bitten project.