org.evomaster.client.java.controller.api.dto.auth

Class AuthenticationDto

java.lang.Object

org.evomaster.client.java.controller.api.dto.auth.AuthenticationDto

public class AuthenticationDto
extends Object

To authenticate a user, would need specific settings, like specific values in the HTTP headers (eg, cookies)

Field Summary

Fields

Modifier and Type	Field and Description
List<HeaderDto>	fixedHeaders The headers needed for authentication.
JsonAuthRPCEndpointDto	jsonAuthEndpoint if the auth is processed based on RPC endpoints, specify what info are required to execute the endpoint
LocalAuthenticationDto	localAuthSetup if the auth is processed with handleLocalAuthenticationSetup specify what info is as input to setup auth with handleLocalAuthenticationSetup
LoginEndpointDto	loginEndpointAuth Used to represent the case in which a login endpoint is used to obtain the auth credentials.
String	name The name given to this authentication info.
Boolean	requireMockHandling Specify that the authentication for this user requires setting up mock responses from external services in the API.

Constructor Summary

Constructors

Constructor and Description
AuthenticationDto()
AuthenticationDto(String name)

Method Summary

Methods inherited from class java.lang.Object

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

Field Detail

name

public String name

The name given to this authentication info. This works as a unique id for this authentication configuration.

requireMockHandling

public Boolean requireMockHandling

Specify that the authentication for this user requires setting up mock responses from external services in the API. This will be done as part of the fuzzing, although only possible for white-box testing. One consequence here is that, even if we provide correct auth info as input, then a request might still fail due to unauthorized access if the fuzzing process does not properly set up these mocked responses in the API itself.

fixedHeaders

public List<HeaderDto> fixedHeaders

The headers needed for authentication. This is used to represent cases in which auth info is static/fixed, eg when passing an id or username/password through a HTTP header (and not using for example a dynamically generated token from a login endpoint first).

loginEndpointAuth

public LoginEndpointDto loginEndpointAuth

Used to represent the case in which a login endpoint is used to obtain the auth credentials. These can be cookies, or a token extracted from the login endpoint's response. This token can then be added to an HTTP header in the following requests.

jsonAuthEndpoint

public JsonAuthRPCEndpointDto jsonAuthEndpoint

if the auth is processed based on RPC endpoints, specify what info are required to execute the endpoint

localAuthSetup

public LocalAuthenticationDto localAuthSetup

if the auth is processed with handleLocalAuthenticationSetup specify what info is as input to setup auth with handleLocalAuthenticationSetup

Constructor Detail

AuthenticationDto

public AuthenticationDto()

AuthenticationDto

public AuthenticationDto(String name)