Digest access authentication: Difference between revisions

Revision as of 15:33, 28 October 2023

Revision as of 02:28, 1 December 2023

Line 1:

'''Digest access authentication''' is one of the agreed-upon methods a [[web server]] can use to negotiate credentials, such as username or password, with a user's [[web browser]]. This can be used to confirm the identity of a user before sending sensitive information, such as online banking transaction history. It applies a [[hash function]] to the username and [[password]] before sending them over the network. In contrast, [[basic access authentication]] uses the easily reversible [[Base64]] encoding instead of hashing, making it non-secure unless used in conjunction with [[Transport Layer Security|TLS]].

{{Short description|Method of negotiating credentials between web server and browser}}

{{HTTP}}

'''Digest access authentication''' is one of the agreed-upon methods a [[web server]] can use to negotiate credentials, such as username or password, with a user's [[web browser]]. This can be used to confirm the identity of a user before sending sensitive information, such as online banking transaction history. It applies a [[hash function]] to the username and [[password]] before sending them over the network. In contrast, [[basic access authentication]] uses the easily reversible [[Base64]] encoding instead of hashing, making it non-secure unless used in conjunction with [[Transport Layer Security|TLS]].

Technically, digest authentication is an application of [[MD5]] [[cryptographic hash]]inghashing with usage of [[cryptographic nonce|nonce]] values to prevent [[replay attack]]sattacks. It uses the [[Hypertext Transfer Protocol|HTTP]] protocol.

== Overview ==