本文整理汇总了C++中AuthenticationClient::receivedCredential方法的典型用法代码示例。如果您正苦于以下问题：C++ AuthenticationClient::receivedCredential方法的具体用法？C++ AuthenticationClient::receivedCredential怎么用？C++ AuthenticationClient::receivedCredential使用的例子？那么, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类AuthenticationClient的用法示例。
在下文中一共展示了AuthenticationClient::receivedCredential方法的3个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的C++代码示例。
示例1: useCredentialForSingleChallenge
void AuthenticationManager::useCredentialForSingleChallenge(uint64_t challengeID, const Credential& credential, const CertificateInfo& certificateInfo)
{
auto challenge = m_challenges.take(challengeID);
ASSERT(!challenge.challenge.isNull());
if (tryUseCertificateInfoForChallenge(challenge.challenge, certificateInfo))
return;
AuthenticationClient* coreClient = challenge.challenge.authenticationClient();
#if USE(NETWORK_SESSION)
// If there is a completion handler, then there is no AuthenticationClient.
// FIXME: Remove the use of AuthenticationClient in WebKit2 once NETWORK_SESSION is used for all loads.
if (challenge.completionHandler) {
ASSERT(!coreClient);
challenge.completionHandler(AuthenticationChallengeDisposition::UseCredential, credential);
return;
}
#else
if (!coreClient) {
// FIXME: The authentication client is null for downloads, but it can also be null for canceled loads.
// We should not call Download::receivedCredential in the latter case.
Download::receivedCredential(challenge.challenge, credential);
return;
}
#endif
ASSERT(coreClient);
coreClient->receivedCredential(challenge.challenge, credential);
}示例2: useCredentialForSingleChallenge
void AuthenticationManager::useCredentialForSingleChallenge(uint64_t challengeID, const Credential& credential, const CertificateInfo& certificateInfo)
{
auto challenge = m_challenges.take(challengeID);
ASSERT(!challenge.challenge.isNull());
#if USE(NETWORK_SESSION)
auto completionHandler = challenge.completionHandler;
#else
ChallengeCompletionHandler completionHandler = nullptr;
#endif
if (tryUseCertificateInfoForChallenge(challenge.challenge, certificateInfo, completionHandler))
return;
AuthenticationClient* coreClient = challenge.challenge.authenticationClient();
#if USE(NETWORK_SESSION)
// If there is a completion handler, then there is no AuthenticationClient.
// FIXME: Remove the use of AuthenticationClient in WebKit2 once NETWORK_SESSION is used for all loads.
if (completionHandler) {
ASSERT(!coreClient);
challenge.completionHandler(AuthenticationChallengeDisposition::UseCredential, credential);
return;
}
#endif
if (coreClient)
coreClient->receivedCredential(challenge.challenge, credential);
else
receivedCredential(challenge.challenge, credential);
}示例3: useCredentialForSingleChallenge
void AuthenticationManager::useCredentialForSingleChallenge(uint64_t challengeID, const Credential& credential, const CertificateInfo& certificateInfo)
{
AuthenticationChallenge challenge = m_challenges.take(challengeID);
ASSERT(!challenge.isNull());
if (tryUseCertificateInfoForChallenge(challenge, certificateInfo))
return;
AuthenticationClient* coreClient = challenge.authenticationClient();
if (!coreClient) {
// FIXME: The authentication client is null for downloads, but it can also be null for canceled loads.
// We should not call Download::receivedCredential in the latter case.
Download::receivedCredential(challenge, credential);
return;
}
coreClient->receivedCredential(challenge, credential);
}