SonicOS/X API Reference Guide

Challenge-Free and Challenge/Response Operation

If the client saves the nonce and opaque values from the authentication stage and uses those with a sequential nonce count to generate Authorization headers in its requests then, so long as those are valid, no challenge is needed, allowing for efficient operation with a single HTTP request/response for each API management operation. It is recommended that this should be the normal method of operation for most clients.

On the other hand, the client can choose to not do this, sending its requests initially without an Authorization header, in which case each request solicits a 401 Unauthorized response with an HTTP digest challenge to which the client can respond. Operating in this way is less efficient, with two request/response exchanges needed for every API management operation, but it means that a utility like curl, which does not support tracking nonces etc. across multiple requests, can be used without needing additional scripting.

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

  • Hidden
  • Hidden

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.
  • Hidden
  • Hidden