AuthenticationRequest
Represents an authentication request.
Whenever a client attempts to load a page protected by HTTP authentication, credentials will need to be provided to authorize access. To allow the client to decide how it wishes to handle authentication, WebKit will fire a #WebKitWebView::authenticate signal with a WebKitAuthenticationRequest object to provide client side authentication support. Credentials are exposed through the #WebKitCredential object.
In case the client application does not wish to handle this signal WebKit will provide a default handler. To handle authentication asynchronously, simply increase the reference count of the WebKitAuthenticationRequest object.
Constructors
Functions
Authenticate the #WebKitAuthenticationRequest.
Determine whether this #WebKitAuthenticationRequest should allow the storage of credentials.
This signal is emitted when the user authentication request succeeded. Applications handling their own credential storage should connect to this signal to save the credentials.
This signal is emitted when the user authentication request is cancelled. It allows the application to dismiss its authentication dialog in case of page load failure for example.
Get the #GTlsPasswordFlags of the %WEBKIT_AUTHENTICATION_SCHEME_CLIENT_CERTIFICATE_PIN_REQUESTED authentication challenge.
Get the #WebKitCredential of the proposed authentication challenge.
Get the authentication scheme of the authentication challenge.
Get the #WebKitSecurityOrigin that this authentication challenge is applicable to.
Determine whether the authentication challenge is associated with a proxy server.
Set whether the authentication method associated with @request should allow the storage of credentials.
Set the #WebKitCredential of the proposed authentication challenge.