RE: Component access to client users identity
From: jzhu (anonymous_at_discussions.microsoft.com)
Date: 03/24/04
- Next message: David Pinz: "Capicom envelopeddata.decrypt failing when content > 64k"
- Previous message: Gavin: "Component access to client users identity"
- In reply to: Gavin: "Component access to client users identity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 24 Mar 2004 06:11:06 -0800
Assuming your COM+ plumming is set up correctly to pass a client identity to the server, get the "domain\name" on the server as:
WindowsIdentity.GetCurrent().Name
----- Gavin wrote: -----
I have an application with a thick client accessing a VB .NET component in COM+ (i.e inheriting from ServicedComponent).
I need this COM+ component to be able to access the NT user name of the client, and potentially the domain name as well. Is there a straight forward way of doing this?
Regards
Gavin
- Next message: David Pinz: "Capicom envelopeddata.decrypt failing when content > 64k"
- Previous message: Gavin: "Component access to client users identity"
- In reply to: Gavin: "Component access to client users identity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
