Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Replacing a Principal Object

Replacing a Principal Object

Applications that provide authentication services must be able to replace the Principal object for a given thread. Further, the security system must help protect the ability to replace Principal objects because a maliciously attached, incorrect Principal compromises the security of your application by claiming an untrue identity or role. Therefore, applications that require the ability to replace Principal objects must be granted the System.Security.Permissions.SecurityPermission object for principal control. (Note that this permission is not required for performing role-based security checks or for creating Principal objects.)

The current Principal object can be replaced by performing the following tasks:

  1. Create the replacement Principal object and associated Identity object, usually after performing authentication.
  2. Create a new System.Security.Permissions.SecurityPermission object, passing the SecurityPermissionAttribute.ControlPrincipal enumeration value to the constructor. (Note that this permission is not necessary for trusted code that simply replaces the permission object, but is necessary when a trusted host is providing the principal to semi-trusted code for role-based verification.)
  3. Attach the new Principal object to the call context, as shown in the following code.
    Thread.CurrentPrincipal = principalObject;
    [Visual Basic]
    Thread.CurrentPrincipal = principalObject
    

See Also

System.Security.Permissions.SecurityPermission | Principal and Identity Objects

Show:
© 2015 Microsoft