void challengeReceived ( nsIHttpChannel channel , char* challenge , PRBool proxyAuth , inout nsISupports sessionState , inout nsISupports continuationState , out PRBool invalidatesIdentity )

Upon receipt of a server challenge, this function is called to determine whether or not the current user identity has been rejected. If true, then the user will be prompted by the channel to enter (or revise) their identity. Following this, generateCredentials will be called.

If the IDENTITY_IGNORED auth flag is set, then the invalidateIdentity return value will be ignored, and user prompting will be suppressed.

Arguments:

channel: the http channel that received the challenge.

challenge: the challenge from the WWW-Authenticate/Proxy-Authenticate server response header. (possibly from the auth cache.)

proxyAuth: flag indicating whether or not challenge is from a proxy.

sessionState: see description below for generateCredentials.

continuationState: see description below for generateCredentials.

invalidatesIdentity

char* generateCredentials ( nsIHttpChannel channel , char* challenge , PRBool proxyAuth , PRUnichar* domain , PRUnichar* user , PRUnichar* password , inout nsISupports sessionState , inout nsISupports continuationState )

Called to generate the authentication credentials for a particular server/proxy challenge. This is the value that will be sent back to the server via an Authorization/Proxy-Authorization header.

This function may be called using a cached challenge provided the authenticator sets the REUSABLE_CHALLENGE flag.

Arguments:

channel: the http channel requesting credentials

challenge: the challenge from the WWW-Authenticate/Proxy-Authenticate server response header. (possibly from the auth cache.)

proxyAuth: flag indicating whether or not challenge is from a proxy.

domain: string containing the domain name (if appropriate)

user: string containing the user name

password: string containing the password

sessionState: state stored along side the user's identity in the auth cache for the lifetime of the browser session. if a new auth cache entry is created for this challenge, then this parameter will be null. on return, the result will be stored in the new auth cache entry. this parameter is non-null when an auth cache entry is being reused.

continuationState: state held by the channel between consecutive calls to generateCredentials, assuming multiple calls are required to authenticate. this state is held for at most the lifetime of the channel.