Enum ClientAssertionKeyFault

Namespace

MailFathom.Common.ClientAssertions

Assembly

MailFathom.Common.dll

Why key material could not be used for the half of the pair it was read as.

public enum ClientAssertionKeyFault

Fields

EncryptedPrivateKey = 2

The material is a password-protected private key, which nothing here unlocks.

ModulusTooShort = 4

The material is an RSA key shorter than the shortest modulus this deployment accepts a signature from.

NotPem = 0

The material is not PEM at all, so nothing about it names a key.

UnsupportedAlgorithm = 3

The material is a key of a kind no permitted signature algorithm covers.

WrongHalf = 1

The material is PEM carrying the other half of the pair: a private key where the public one belongs, or the reverse.

The one fault worth telling apart from every other, because it is the mistake the method exists to make impossible — a deployment configured with a private key would be holding exactly what key-pair authentication is for not holding.

Remarks

The vocabulary reaches an operator rather than a client: the deployment reports it at startup against the configuration path the material was named at, and mfctl reports it against the file the operator passed. No refusal of a request ever carries one, because by the time a request is judged the material has already proven usable.