Package com.webauthn4j.validator

Class CoreAuthenticationDataValidator

java.lang.Object

com.webauthn4j.validator.CoreAuthenticationDataValidator

public class CoreAuthenticationDataValidator
extends Object

Constructor Summary

Constructors

Modifier	Constructor	Description
	CoreAuthenticationDataValidator()
	CoreAuthenticationDataValidator(@NonNull List<CustomCoreAuthenticationValidator> customAuthenticationValidators)
protected	CoreAuthenticationDataValidator(@NonNull List<CustomCoreAuthenticationValidator> customAuthenticationValidators, @NonNull AssertionSignatureValidator assertionSignatureValidator)

Method Summary

Modifier and Type	Method	Description
protected @NonNull CoreAuthenticationObject	createCoreAuthenticationObject(@NonNull CoreAuthenticationData authenticationData, @NonNull CoreAuthenticationParameters authenticationParameters)
@NonNull List<CustomCoreAuthenticationValidator>	getCustomAuthenticationValidators()
@NonNull CoreMaliciousCounterValueHandler	getMaliciousCounterValueHandler()
void	setMaliciousCounterValueHandler(@NonNull CoreMaliciousCounterValueHandler coreMaliciousCounterValueHandler)
void	validate(@NonNull CoreAuthenticationData authenticationData, @NonNull CoreAuthenticationParameters authenticationParameters)	It is up to caller responsibility to inject challenge into clientData and validate it equals to challenge stored in server side

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

CoreAuthenticationDataValidator

public CoreAuthenticationDataValidator(@NonNull List<CustomCoreAuthenticationValidator> customAuthenticationValidators)

CoreAuthenticationDataValidator

public CoreAuthenticationDataValidator()

CoreAuthenticationDataValidator

protected CoreAuthenticationDataValidator(@NonNull List<CustomCoreAuthenticationValidator> customAuthenticationValidators,
 @NonNull AssertionSignatureValidator assertionSignatureValidator)

Method Details

validate

public void validate(@NonNull CoreAuthenticationData authenticationData,
 @NonNull CoreAuthenticationParameters authenticationParameters)

It is up to caller responsibility to inject challenge into clientData and validate it equals to challenge stored in server side

Parameters:

authenticationData - authentication data

authenticationParameters - authentication parameters

createCoreAuthenticationObject

protected @NonNull CoreAuthenticationObject createCoreAuthenticationObject(@NonNull CoreAuthenticationData authenticationData,
 @NonNull CoreAuthenticationParameters authenticationParameters)

getMaliciousCounterValueHandler

public @NonNull CoreMaliciousCounterValueHandler getMaliciousCounterValueHandler()

setMaliciousCounterValueHandler

public void setMaliciousCounterValueHandler(@NonNull CoreMaliciousCounterValueHandler coreMaliciousCounterValueHandler)

getCustomAuthenticationValidators

public @NonNull List<CustomCoreAuthenticationValidator> getCustomAuthenticationValidators()