nerdexam
Cisco

350-901 · Question #91

What are two methods for sending bearer access tokens in resource requests to servers? (Choose two)

The correct answer is C. in the HTTP request entity-body D. in the "Authorization" request header field. RFC 6750 defines three methods for sending OAuth 2.0 bearer tokens: the Authorization request header field and the form-encoded entity-body are two of the three valid methods.

Using APIs

Question

What are two methods for sending bearer access tokens in resource requests to servers? (Choose two)

Options

  • Ain plaintext for user access
  • Bin the HTTP API schema
  • Cin the HTTP request entity-body
  • Din the "Authorization" request header field
  • Ein the HTTP request URI

How the community answered

(27 responses)
  • B
    7% (2)
  • C
    89% (24)
  • E
    4% (1)

Why each option

RFC 6750 defines three methods for sending OAuth 2.0 bearer tokens: the Authorization request header field and the form-encoded entity-body are two of the three valid methods.

Ain plaintext for user access

Sending tokens in plaintext without a defined transport mechanism is not a valid bearer token transmission method and would be a security violation, as RFC 6750 requires TLS protection.

Bin the HTTP API schema

There is no specification called 'HTTP API schema' as a bearer token transmission method; this is not defined in RFC 6750 or any related OAuth 2.0 standard.

Cin the HTTP request entity-bodyCorrect

Sending the bearer token in the HTTP request entity-body is a valid method defined in RFC 6750 Section 2.2, where the token is included as the 'access_token' parameter in a form-encoded request body with Content-Type 'application/x-www-form-urlencoded'.

Din the "Authorization" request header fieldCorrect

Including the bearer token in the 'Authorization' request header field using the format 'Authorization: Bearer <token>' is the most widely used method, defined in RFC 6750 Section 2.1, and is preferred because it keeps the token out of server logs.

Ein the HTTP request URI

While RFC 6750 Section 2.3 does mention the URI query parameter method, it is explicitly described as a last resort due to security risks from tokens appearing in server logs and browser history.

Concept tested: OAuth 2.0 bearer token transmission methods per RFC 6750

Source: https://datatracker.ietf.org/doc/html/rfc6750

Topics

#API Authentication#Bearer Tokens#HTTP Headers#API Security

Community Discussion

No community discussion yet for this question.

Full 350-901 Practice