MSIPHttpDigestChallengeObserver2 Class Reference

class MSIPHttpDigestChallengeObserver2

The user should implement this interface if it intends to provide HTTP Digest credentials upon received challenges from the SIP servers on the signaling path. The user should provide credentials or ignore the challenge using functions defined in CSIPHttpDigest class.

Applications are encouraged to use implement below interface which provides functions to extract multiple challenges. MSIPHttpDigestChallengeObserver2 class is compliant to RFC 3261

n/a

Public Member Functions
voidChallengeReceived(const CSIPClientTransaction &)
voidChallengeReceived(const CSIPRefresh &)

Member Functions Documentation

ChallengeReceived(const CSIPClientTransaction &)

voidChallengeReceived(const CSIPClientTransaction &aTransaction)[pure virtual]

A SIP request resulted in 401/407 response that contains 1..n challenges. The challenges can be obtained from Proxy-Authenticate- and/or WWW-Authenticate-headers in the CSIPResponseElements attached to the CSIPClientTransaction. The user must call CSIPHttpDigest::SetCredentialsL or CSIPHttpDigest::IgnoreChallenge for each challenge.

Parameters

const CSIPClientTransaction & aTransactiontransaction which was completed with a response containing HTTP Digest challenge.

ChallengeReceived(const CSIPRefresh &)

voidChallengeReceived(const CSIPRefresh &aRefresh)[pure virtual]

A refreshed SIP request resulted in 401/407 response that contains 1..n challenges. The challenges can be obtained from Proxy-Authenticate- and/or WWW-Authenticate-headers in the CSIPResponseElements attached to the CSIPClientTransaction attached to the CSIPRefresh. The user must call CSIPHttpDigest::SetCredentialsL or CSIPHttpDigest::IgnoreChallenge for each challenge.

Parameters

const CSIPRefresh & aRefreshthe refresh for which a transaction completed with a response containing HTTP Digest challenge.