… a client password MAY use the HTTP Basic authentication scheme as defined in [ RFC2617 ] to authenticate with the authorization server. The client identifier is encoded using the "application/x-www-form-urlencoded" encoding algorithm per Appendix B , and the encoded value is use…
…sly described in "HTTP Authentication: Basic and Digest Access Authentication" [RFC2617] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [RFC2616] The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered auth…
… a client password MAY use the HTTP Basic authentication scheme as defined in [ RFC2617 ] to authenticate with the authorization server. The client identifier is encoded using the "application/x-www-form-urlencoded" encoding algorithm per Appendix B , and the encoded value is use…
…etwork as cleartext. The "Basic" scheme previously was defined in Section 2 of [RFC2617] . This document updates the definition, and also addresses internationalization issues by introducing the 'charset' authentication parameter ( Section 2.1 ). Other documents updating RFC 2617…
…etwork as cleartext. The "Basic" scheme previously was defined in Section 2 of [RFC2617] This document updates the definition, and also addresses internationalization issues by introducing the 'charset' authentication parameter ( Section 2.1 ). Other documents updating RFC 2617 a…
…ntations MUST be capable of being configured to use HTTP Basic Authentication [ RFC2617 ] in conjunction with a connection made with TLS 1.0 [ RFC2246 ] or a subsequent standards-track version of TLS (such as [ RFC4346 ]), supporting the conventions for using HTTP over TLS descri…
…ntations MUST be capable of being configured to use HTTP Basic Authentication [ RFC2617 ] in conjunction with a connection made with TLS 1.0 [ RFC2246 ] or a subsequent standards-track version of TLS (such as [ RFC4346 ]), supporting the conventions for using HTTP over TLS descri…
…etwork as cleartext. The "Basic" scheme previously was defined in Section 2 of [RFC2617] This document updates the definition, and also addresses internationalization issues by introducing the 'charset' authentication parameter ( Section 2.1 ). Other documents updating RFC 2617 a…
…ly described in "HTTP Authentication: Basic and Digest Access Authentication" [ RFC2617 ] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [ RFC2616 ]. The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered …
…ly described in "HTTP Authentication: Basic and Digest Access Authentication" [ RFC2617 ] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [ RFC2616 ]. The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered …
…ly described in "HTTP Authentication: Basic and Digest Access Authentication" [ RFC2617 ] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [ RFC2616 ]. The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered …
…ly described in "HTTP Authentication: Basic and Digest Access Authentication" [ RFC2617 ] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [ RFC2616 ]. The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered …
…ation, as the HTTP protocol already has a number of authentication mechanisms [ RFC2617 ]. Some authentication mechanism (such as HTTP Digest Authentication, which all WebDAV compliant implementations are required to support) must be available to validate the identity of a princi…
…ly described in "HTTP Authentication: Basic and Digest Access Authentication" [ RFC2617 ] and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" [ RFC2616 ]. The IANA Authentication Scheme Registry ( Section 5.1 ) lists registered …
…nsitive data MUST be authenticated using digest authentication as specified in [RFC2617], with the exception of a device that is being bootstrapped for the first time via the device profile. The resulting TLS channel also provides data integrity and data confidentiality. 5.2.3. S…