public enum FailureMode

What a protected host should do when a token cannot be obtained.

This is deliberately a per-host decision. An app typically wants CLOSED on the handful of endpoints that move money or read personal data, and OPEN everywhere else, so that a shield service outage degrades one feature rather than bricking the app.

Enum constants

`OPEN`	Send the request without a token.
`CLOSED`	Refuse to send the request, failing it with a `ShieldException` carrying the reason.

Methods

`public static` `FailureMode[] values()`
`public static` `FailureMode valueOf(String name)`

Inherited methods

From Enum

clone, setEnumValues, getEnumValues, valueOf, equals, hashCode, toString, compareTo, name, ordinal, getDeclaringClass

From Object

getClass, notify, notifyAll, wait, wait, wait

Enum constant details

OPEN

OPEN

Send the request without a token. The customer’s backend still decides what to do with an unattested request; this only means the client does not block it locally.

This is the default, and it is the only behaviour available when the app was built without the enterprise engine.

CLOSED

CLOSED

Refuse to send the request, failing it with a ShieldException carrying the reason. Use this only where a false negative is more acceptable than an unattested call, and only after reading ShieldStatus.isTransient() – most token failures are network problems, not compromised devices.

Method details

values

public static FailureMode[] values()

valueOf

public static FailureMode valueOf(String name)