store

The contract of this function is that it stores challenges regardless of their contents and performs no sanity checks. Reason: Strong cryptographic nonces are assumed, making collisions unrealistic

Implementations may throw if they cannot store the challenge. For example, InMemoryChallengeCache throws InMemoryChallengeCache.ChallengeCacheFullException when its bounded in-memory capacity is exhausted.