I'm using it with deepbit's pool (deepbit.net) it also works with btcmine.com's miner
I dug through the source code of Ufasoft's miner.
Basically, most miners (poclbm, diablominer, rpc-miner, jgarzik's cpu miner) work like this:
Client (Request for Getwork w/ Authorization Headers included) --> Server
Server (Respond with Getwork) --> Client
Client (Send Hash from Getwork) --> Server
Server (Respond with Accepted, or Invalid/Stale) --> Client
Ufasoft's Miner works like this:
Client (Request Getwork) --> Server
Server (Prompt for Authorization) --> Client
Client (Respond with Credentials) --> Server
Server (Respond with Getwork) --> Client
Client (Send Hash from Getwork) --> Server
Server (Prompt for Authorization) --> Client
Client (Respond with Credentials) --> Server
Server (Respond with Accepted, or Invalid/Stale) --> Client
Twice as much network traffic, and incompatible with our pool simply because they don't include the credentials in the headers on every request.
Maybe you can email ufasoft about it and see if they can modify the way their miner works.
I'd like to point out my RPC Proxy fixes this issue with Ufasoft's client, as it doesn't use any authorization locally, and always sends authorization to the server.
Regards
elFarto