Skip to content

Update credentials-processes-in-windows-authentication.md #7963

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update credentials-processes-in-windows-authentication.md #7963

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...urity/windows-authentication/credentials-processes-in-windows-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ This topic contains the following sections:
- [Certificates in Windows authentication](#BKMK_CertificatesInWindowsAuthentication)

## <a name="BKMK_CrentialInputForUserLogon"></a>Credential input for user logon
In Windows Server 2008 and Windows Vista, the Graphical Identification and Authentication (GINA) architecture was replaced with a credential provider model, which made it possible to enumerate different logon types through the use of logon tiles. Both models are described below.
Starting in Windows Server 2008 and Windows Vista, the Graphical Identification and Authentication (GINA) architecture was replaced with a credential provider model, which made it possible to enumerate different logon types through the use of logon tiles. Both models are described below.

**Graphical Identification and Authentication architecture**

Expand Down Expand Up @@ -296,7 +296,7 @@ Similarly, the remote host or local computer must determine if the certificate p
To produce a certificate, authentication data passes through hash algorithms, such as Secure Hash Algorithm 1 (SHA1), to produce a message digest. The message digest is then digitally signed by using the sender's private key to prove that the message digest was produced by the sender.

> [!NOTE]
> SHA1 is the default in Windows 7 and Windows Vista, but was changed to SHA2 in Windows 8.
> SHA1 is the default in Windows 7 and Windows Vista, but was changed to SHA2 starting in Windows 8.

**Smart card authentication**

Expand Down