![]() ![]() Symptoms Problem Scenario 1 (logon/logoff)Īn administrator wants to enforce Smart Card (SC) Logon authentication when users access certain security-sensitive resources. This is because resources that are accessed after an interactive user logon can’t be reliably protected by using AMA. ![]() The behavior of AMA in these scenarios is "by design" and can be summarized as follows:ĪMA is intended to protect network resources.ĪMA can neither identify nor enforce the interactive logon type (smart card or user name/password) for the user's local computer. This article focuses on two problem scenarios: logon/logoff and lock/unlock. This access is based on whether the user logs on by using a certificate-based logon method and the type of certificate that's used to log on. This makes it possible for network resource administrators to control the access to resources, such as files, folders, and printers. IntroductionĪMA adds an administrator-designated, universal group membership to a user's access token when the user's credentials are authenticated during logon by using a certificate-based logon method. ![]() This article discusses how to use Authentication Mechanism Assurance (AMA) in interactive logon scenarios. Windows Server 2012 R2 Standard Windows Server 2012 R2 Datacenter Windows 8.1 Pro Windows 8.1 Enterprise Windows Server 2012 Standard Windows Server 2012 Standard Windows Server 2012 Datacenter Windows Server 2012 Datacenter Windows 8 Pro Windows 8 Enterprise Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows 7 Enterprise Windows 7 Professional More. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |