Module com.webauthn4j.core

Package com.webauthn4j.verifier

Class CoreAuthenticationDataVerifier

java.lang.Object

com.webauthn4j.verifier.CoreAuthenticationDataVerifier

public class CoreAuthenticationDataVerifier
extends Object

Constructor Summary

Constructors

Modifier	Constructor	Description
	CoreAuthenticationDataVerifier()
	CoreAuthenticationDataVerifier(@NotNull List<CustomCoreAuthenticationVerifier> customAuthenticationVerifiers)
protected	CoreAuthenticationDataVerifier(@NotNull List<CustomCoreAuthenticationVerifier> customAuthenticationVerifiers, @NotNull AssertionSignatureVerifier assertionSignatureVerifier)

Method Summary

Modifier and Type	Method	Description
protected @NotNull CoreAuthenticationObject	createCoreAuthenticationObject(@NotNull CoreAuthenticationData authenticationData, @NotNull CoreAuthenticationParameters authenticationParameters)
@NotNull List<CustomCoreAuthenticationVerifier>	getCustomAuthenticationVerifiers()
@NotNull CoreMaliciousCounterValueHandler	getMaliciousCounterValueHandler()
void	setMaliciousCounterValueHandler(@NotNull CoreMaliciousCounterValueHandler coreMaliciousCounterValueHandler)
void	verify(@NotNull CoreAuthenticationData authenticationData, @NotNull CoreAuthenticationParameters authenticationParameters)	It is up to caller responsibility to inject challenge into clientData and verify 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

CoreAuthenticationDataVerifier

public CoreAuthenticationDataVerifier(@NotNull
 @NotNull List<CustomCoreAuthenticationVerifier> customAuthenticationVerifiers)

CoreAuthenticationDataVerifier

public CoreAuthenticationDataVerifier()

CoreAuthenticationDataVerifier

protected CoreAuthenticationDataVerifier(@NotNull
 @NotNull List<CustomCoreAuthenticationVerifier> customAuthenticationVerifiers,
 @NotNull
 @NotNull AssertionSignatureVerifier assertionSignatureVerifier)

Method Details

verify

public void verify(@NotNull
 @NotNull CoreAuthenticationData authenticationData,
 @NotNull
 @NotNull CoreAuthenticationParameters authenticationParameters)

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

Parameters:

authenticationData - authentication data

authenticationParameters - authentication parameters

createCoreAuthenticationObject

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

getMaliciousCounterValueHandler

@NotNull
public @NotNull CoreMaliciousCounterValueHandler getMaliciousCounterValueHandler()

setMaliciousCounterValueHandler

public void setMaliciousCounterValueHandler(@NotNull
 @NotNull CoreMaliciousCounterValueHandler coreMaliciousCounterValueHandler)

getCustomAuthenticationVerifiers

@NotNull
public @NotNull List<CustomCoreAuthenticationVerifier> getCustomAuthenticationVerifiers()