Re: Communicating with DCOM server using another user account

thanks Brian. I have done several tests.
CoSetProxyBlanket would probably be fine for accessing
the server remotely. One specific client, however, needs to run on the same
machine as the server.
CoSetProxyBlanket is documented to not use the specified AuthInfo
parameter for client and server on the same machine.
In a test program I tried specifying credentials to CoCreateInstanceEx
and also in a call to CoInitializeSecurity but both didn't work!
The only method that worked for me was to write a launcher app that
uses CreateProcessWithLogonW to launch the client program.

Is there any method at all that allows me to call methods of a
DCOM server locally with different credentials?

thanks for the help,
Nick


Hmm..... so on the server side, one hand is tied behind your back since
user B is required. And on the client side, your other hand is tied behind
your back since you can't call CoCreateInstanceEx to set the user
authentication to user B.

Short of untying your hands, I'll give you yet another solution: call
CoSetProxyBlanket as soon as you acquire the remote interface, setting the
RPC_AUTH_IDENTITY_HANDLE parameter to user B.

Brian




.

Relevant Pages

  • Re: Communicating with DCOM server using another user account
    ... machine as the server. ... CoSetProxyBlanket is documented to not use the specified AuthInfo ... parameter for client and server on the same machine. ... The only method that worked for me was to write a launcher app that ...
    (microsoft.public.win32.programmer.ole)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
Loading