FPCNonWindowsUser Object
The FPCNonWindowsUser object represents a single user who is authenticated using an authentication scheme other than that of Active Directory. Each non-Windows user is defined by a user name and a namespace that identifies the applicable authentication scheme. Examples of non-Windows users include RADIUS and SecurID users. You can manage which non-Windows users are included in a user set using the NonWindowsUsers property of an FPCUserSet object. For more information about the different kinds of users in Forefront TMG and about user sets, see Defining Groups of Users.
Non-Windows users can also be domain users that a Forefront TMG computer belonging to a workgroup can authenticate by communicating with a domain controller using the Lightweight Directory Access Protocol (LDAP). These users are known as LDAP users. The definition of each LDAP user also includes the user's realm and display name.
This object is created as an element of an FPCNonWindowsUsers collection.
Click here to see the Forefront TMG object hierarchy.
Methods
The FPCNonWindowsUser object defines the following methods.
Method | Description |
---|---|
Reads the object's properties from persistent storage, overwriting any changes that have not been saved. |
|
Writes the current values of the object's properties to persistent storage. |
Properties
The FPCNonWindowsUser object defines the following properties.
Property | Description |
---|---|
Gets or sets the display name of the user. |
|
Gets the authentication namespace for the user. |
|
Gets or sets the name of the LDAP server set that will be used for the user. |
|
Gets or sets the user name. |
Interfaces for C++ Programming
This object implements the IFPCNonWindowsUser and IFPCNonWindowsUser2 interfaces.
Requirements
Client | Requires Windows 7 or Windows Vista. |
Server | Requires Windows Server 2008 R2 or Windows Server 2008 x64 Edition with SP2. |
Version | Requires Forefront Threat Management Gateway (TMG) 2010. |
IDL | Declared in Msfpccom.idl. |
See Also
Send comments about this topic to Microsoft
Build date: 6/30/2010