Authentication & Configuration
In order to authenticate to Gremlin, you must provide the following configuration values to your application.
GREMLIN_ALFI_IDENTIFIER: A unique identifier for the application. This will be used to distinguish all of the application instances from one another
GREMLIN_TEAM_ID: The Team ID that this application belongs to. Only users in that team may conduct attacks on it.
GREMLIN_TEAM_CERTIFICATE_OR_FILE: Certificate for authenticating to Gremlin. See below for syntax on permissible values.
GREMLIN_TEAM_PRIVATE_KEY_OR_FILE: Private key for authenticating to Gremlin. See below for syntax on permissible values.
You may set these as environment variables or in a
gremlin.properties file on the classpath. Certificates can be downloaded for each team from the Settings Page.
As a raw value
Or pointing to a file
The following keys may be set to tune how ALFI operates.
GREMLIN_ALFI_ENABLED: If set to anything other than
true, all functionality is turned off. This is designed to give you the ability to safely deploy ALFI, knowing you’ve got a simple off-switch. When the functionality is off, no failures are ever injected by ALFI, no calls are made to the API, and no logging past configuration-time occurs.
GREMLIN_REFRESH_INTERVAL_MS: You may optionally provide this value to set the frequency with which the library will contact the Gremlin API. Minimum of 1000 (1 second), maximum of 300000 (5 minutes). Default of 10000 (10 seconds). This determines how quickly your application reacts to attacks being halted or created and the amount of network traffic generated by the library.
http_proxy: You may specify a proxy for traffic from the ALFI library back to the Gremlin control plane. This may optionally include basic auth.