Amebis/GEANTLink
1
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 50 Wiki Activity

EapPeerMethodResult's fIsSuccess and dwFailureReasonCode management revised to guarantee configuration gets saved

Browse Source
This commit is contained in:
Simon Rozman
2016-09-06 09:57:34 +02:00
parent ff0b6c5ee4
commit b255aa6505
4 changed files with 7 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
lib/TLS/src/Method.cpp
View File

@@ -530,9 +530,6 @@ void eap::method_tls::get_result(
// Clear credentials as failed.
m_cfg.m_auth_failed = false;
ppResult->fIsSuccess = TRUE;
ppResult->dwFailureReasonCode = ERROR_SUCCESS;
#if EAP_TLS < EAP_TLS_SCHANNEL
// Update configuration with session resumption data.
m_cfg.m_session_id = m_session_id;
@@ -595,11 +592,6 @@ void eap::method_tls::get_result(
// TODO: Research how a Schannel session context can be cleared not to resume.
#endif
// Do not report failure to EapHost, as it will not save updated configuration then. But we need it to save it, to alert user on next connection attempt.
// EapHost is well aware of the failed condition.
//ppResult->fIsSuccess = FALSE;
//ppResult->dwFailureReasonCode = EAP_E_AUTHENTICATION_FAILED;
break;
default: