Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:SIP authentication with HTTP Digest credentials

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.



Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition, FP1
S60 3rd Edition FP1
S60 3rd Edition (initial release)
Article
Created: User:Technical writer 2 (04 Jul 2007)
Last edited: hamishwillee (14 Jun 2012)

Overview

SIP authentication with HTTP Digest credentials

Description

CSIPHttpDigest and MSIPHttpDigestChallengeObserver classes can be used for setting the Proxy Authentication Header parameters programmatically when a SIP client application is not using a SIP profile.

Solution

Create a CSIPHttpDigest object in ConstructL() of the engine class, derive from MSIPHttpDigestChallengeObserver, and implement the ChallengeReceived() callback function.
The SIP server in the signalling chain can challenge any SIP request initiated by the application with an HTTP Digest challenge by sending one of the following responses:
  401 (User Authentication Required)
  407 (Proxy Authentication Required)
  494 (Security Agreement Required)
When a SIP client receives the SIP response 407, 401, or 494 from the server, it automatically calls the MSIPHttpDigestChallengeObserver::ChallengeReceived() callback function.
If the client accepts the challenge, the callback function must call CSIPHttpDigest::SetCredentialsL(), specifying the user name, password, and the realm passed to the callback function. The SIP stack resends the original SIP request within the HTTP Digest response.
If the client rejects the challenge, the callback function must call CSIPHttpDigest::IgnoreChallenge(), specifying the realm passed to the callback function.
The SIP stack calls the callback function MSIPConnectionObserver::ErrorOccured(), passing the error code KErrSIPForbidden.
If the SIP client application does not wish to receive HTTP Digest challenges, it must not create a CSIPHttpDigest object. In this event, the SIP stack calls the callback function MSIPConnectionObserver::ErrorOccured(), passing the error code KErrSIPForbidden.

This page was last modified on 14 June 2012, at 07:47.
75 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×