> I have an application that wants to implement its own security model on
> its own objects.
[quoted text clipped - 6 lines]
>
> why?
Because it's the canonical format for user identifiers in a domain
environment, that's why.
You can identify a user with a UPN or with domain\user in modern versions of
Windows, or as domain\user in older versions (NT 4.0 and before, IIRC).
So, it makes some sense to use domain\user format.
In Win32 API, you'd use CrackSingleName.
In .NET, you can use WindowsIdentity, which takes a UPN string argument in
its constructor, and has a Name() member to return the domain\user format.
What are you waiting for?
Alun.
~~~~
[Please don't email posters, if a Usenet response is appropriate.]

Signature
Texas Imperial Software | Find us at http://www.wftpd.com or email
23921 57th Ave SE | alun@wftpd.com.
Washington WA 98072-8661 | WFTPD, WFTPD Pro are Windows FTP servers.
Fax/Voice +1(425)807-1787 | Try our NEW client software, WFTPD Explorer.
I suggest doing a p/invoke to the Windows TranslateName API.
Joe K.
> Hi,
>
[quoted text clipped - 15 lines]
>
> Bob