Which authentication method is used when the REST API of the Cisco UCS Director is accessed?

Question

Options

• ABearer (Bearer Token))
• BHTTP Basic Auth
• CRestAuth (User's Auth Token))
• DX-Cloupia-Request-Key: ((User's Auth Token))

• A
  2% (1)
• B
  4% (2)
• C
  9% (5)
• D
  86% (49)

Explanation

Cisco UCS Director's REST API uses a proprietary header-based authentication scheme where the client must include X-Cloupia-Request-Key as an HTTP header with the user's API access token - this is unique to UCS Director and is not a standard auth protocol. Option A (Bearer Token) is an OAuth 2.0 standard used by many modern APIs but is not how UCS Director authenticates requests. Option B (HTTP Basic Auth) sends Base64-encoded credentials in an Authorization header and is a generic HTTP standard, not UCS Director's mechanism. Option C is a plausible-sounding distractor - there is no standard auth scheme called "RestAuth," and UCS Director does not use that header name.

Memory tip: Think of the X in X-Cloupia-Request-Key as a custom/eXtension header (HTTP custom headers are prefixed with X-), and "Cloupia" was the company Cisco acquired to build UCS Director - so the header literally carries the product's heritage in its name.

No community discussion yet for this question.