156-215.80 · Question #336
Session unique identifiers are passed to the web api using which http header option?
The correct answer is C. Proxy-Authorization. Note - the provided correct answer (C: Proxy-Authorization) appears to be a question bank error; Check Point's Web API uses the custom HTTP header 'X-chkp-sid' (option A) to pass session unique identifiers.
Question
Session unique identifiers are passed to the web api using which http header option?
Options
- AX-chkp-sid
- BAccept-Charset
- CProxy-Authorization
- DApplication
How the community answered
(23 responses)- A4% (1)
- C91% (21)
- D4% (1)
Why each option
Note - the provided correct answer (C: Proxy-Authorization) appears to be a question bank error; Check Point's Web API uses the custom HTTP header 'X-chkp-sid' (option A) to pass session unique identifiers.
Per the provided answer key this is marked wrong, but 'X-chkp-sid' is the actual Check Point-defined HTTP header used to carry session identifiers in all authenticated Web API requests after a successful login call.
Accept-Charset is a standard HTTP content negotiation header indicating acceptable character encodings, and has no role in Check Point session management.
Per the provided answer key, Proxy-Authorization is marked correct, but Check Point's official Management API documentation specifies that session unique identifiers are passed via the custom HTTP header 'X-chkp-sid', which is option A - the answer key for this question appears to contain an error and should be A.
Application is not a recognized standard or Check Point-defined HTTP header and is not used to transmit session identifiers to the Management API.
Concept tested: Check Point Web API session identifier HTTP header
Source: https://sc1.checkpoint.com/documents/latest/APIs/
Topics
Community Discussion
No community discussion yet for this question.