From aac9c2a047467dd18f53b0ae940aa30f1c0ae216 Mon Sep 17 00:00:00 2001 From: Nathaniel McCallum Date: Tue, 16 Oct 2012 12:40:15 -0400 Subject: Handle concat OTP responder case --- src/include/krb5/krb5.hin | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'src/include') diff --git a/src/include/krb5/krb5.hin b/src/include/krb5/krb5.hin index f338689f6..13ada8f78 100644 --- a/src/include/krb5/krb5.hin +++ b/src/include/krb5/krb5.hin @@ -6427,6 +6427,15 @@ krb5_prompter_posix(krb5_context context, void *data, const char *name, */ #define KRB5_RESPONDER_OTP_FLAGS_NEXTOTP (1 << 2) +/** + * This flag indicates that the PIN MUST be returned as a separate item. This + * flag only takes effect if KRB5_RESPONDER_OTP_FLAGS_COLLECT_PIN is set. If + * this flag is not set, the responder may either concatenate PIN + token value + * and store it as "value" in the answer or it may return them separately. If + * they are returned separately, they will be concatenated internally. + */ +#define KRB5_RESPONDER_OTP_FLAGS_SEPARATE_PIN (1 << 3) + typedef struct krb5_responder_context_st *krb5_responder_context; /** -- cgit