RETVAL_OK = 0
Test was executed and the result was as expected.
Test suite to verify that an EAP setup is actually working as advertised in the real world. Can only be used if CONFIG_DIAGNOSTICS['RADIUSTESTS'] is configured.
Its main purpose is to initialise some error messages.
__construct( realm, outerUsernameForChecks, mixed|string|int supportedEapTypes = , mixed|string|int expectedServerNames = , mixed|string|int expectedCABundle = ) :
Constructor for the EAPTests class. The single mandatory parameter is the realm for which the tests are to be carried out.
Logs the start of lifetime of the entity to the debug log on levels 3 and higher.
(array of integer representations of EAP types)
(array of strings)
(array of PEM blocks)
getAttributeValue(mixed|string|int attributeArray, string|int index1, string|int index2) :
This is a helper fuction to retrieve a value from two-dimensional arrays The function tests if the value for the first indes is defined and then the same with the second and finally returns the value if something on the way is not defined, NULL is returned
createTemporaryDirectory( purpose = installer, failIsFatal = 1) : mixed|string|int
create a temporary directory and return the location
one of 'installer', 'logo', 'test' defined the purpose of the directory
decides if a creation failure should cause an error; defaults to true
the tuple of: base path, absolute path for directory, directory name
udpReachability( probeindex, opnameCheck = TRUE, frag = TRUE) :
This function performs actual authentication checks with MADE-UP credentials.
Its purpose is to check if a RADIUS server is reachable and speaks EAP. The function fills array RADIUSTests::UDP_reachability_result[$probeindex] with all check detail in case more than the return code is needed/wanted by the caller
refers to the specific UDP-host in the config that should be checked
should we check choking on Operator-Name?
should we cause UDP fragmentation? (Warning: makes use of Operator-Name!)
udpLogin( probeindex, mixed|string|int eaptype, innerUser, password, opnameCheck = TRUE, frag = TRUE, clientcertdata = NULL) :
The big Guy. This performs an actual login with EAP and records how far it got and what oddities were observed along the way
the probe we are connecting to (as set in product config)
EAP type to use for connection
inner username to try
password to try
whether or not we check with Operator-Name set
whether or not we check with an oversized packet forcing fragmentation
client certificate credential to try
overall return code of the login test