(1) ticket: provides access to the attributes and values of a ticket. These tickets are used for forms authentication and user identification. You can use the ticket attribute of the formsidentity class to access the formsauthenticationticket of the authenticated user. You can access the current formsidentity object by forcibly converting the identity attribute of the current user to formsidentity.
(2) token: the access tag handle associated with the current execution thread, used to obtain the user's windows Account tag. Generally, the account tag is retrieved by calling unmanaged code (such as calling the win32 api logonuser function.
(3) identity: identity encapsulates information about users or entities being verified. At the most basic level, identity contains the name and authentication type. The name can be a user name or windows Account name, and the authentication type can be supported logon protocol (such as kerberos v5) or custom value .. Net framework defines a genericidentity object and a more dedicated windowsidentity object. The former can be used in most custom login schemes, the latter can be used when you want your application to depend on windows authentication. In addition, you can define your own identification class to encapsulate user information.
(4) principal: principal indicates the security context of the Code runtime. Applications that implement role-based security are granted permissions based on the roles associated with the subject object. Similar to the identity object,. net framework provides the genericprincipal object and windowsprincipal object. You can also define your own custom subject class.