I've successfully deployed Windows Server Service Bus on on a stand-alone SERVER machine(workgroup) for testing purposes.
The client application which needs connection to the SB is written/tested on a CLIENT machine on a company network (domain). I've successfully established authentication by creating the same local account (with same password) twice (SERVER+CLIENT) and starting the client application with runas /user:commonaccount.
This is good for testing purposes but still feels like a workaround. Even more when there is a client API function calledCreateWindowsTokenProvider.How come the code seems to ignore the speficied account there?
CreateWindowsTokenProvider(newSystem.Collections.Generic.List<Uri>() { uri }, newSystem.Net.NetworkCredential("CommonAccount","CommonPassword"));
Code is always using the 'currently logged in account' ; unless using runas command. Confusing!