SonicOS/X API Reference Guide

Operation After Non-Digest Authentication

The API client needs to know the values (realm, nonce, opaque and qop) for session security. After initial user authentication by the digest scheme, it already has those and can immediately start sending API requests with digests calculated from them. But if a different mechanism is used for that, the client has two choices:

  • The client can send the first request after authentication with no Authorization header, which provokes a digest challenge giving all the relevant data.

  • On success of any authentication mechanism, other than HTTP digest authentication, if session security is enabled on the API then the “200 OK” response includes an Authentication-Info header giving the data as follows:

    HTTP/1.0 200 OK

    Server: SonicWALL

    Authentication-Info: Digest algorithm=SHA-256, realm="admin-users@a.b.c.d",

    qop="auth", nonce=”…”, opaque=”…"

    This follows the model of the Authentication-Info header specified in RFC-7616, but it is a proprietary use of it. Clients can ignore this header (proceeding as per the first bullet option above) but utilizing the data returned in it to avoid the need for the challenge/response handshake when the first post-authentication API management request is sent.

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