From 21ff4f920e4ff7c1e2870024f007f067fc3cf6c8 Mon Sep 17 00:00:00 2001 From: Nathaniel McCallum Date: Thu, 20 Feb 2014 13:21:32 -0500 Subject: Rework how otptoken defaults are handled We had originally decided to provide defaults on the server side so that they could be part of a global config for the admin. However, on further reflection, only certain defaults really make sense given the limitations of Google Authenticator. Similarly, other defaults may be token specific. Attempting to handle defaults on the server side also makes both the UI and the generated documentation unclear. Reviewed-By: Jan Cholasta --- VERSION | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'VERSION') diff --git a/VERSION b/VERSION index b1dcb9c05..64472ada1 100644 --- a/VERSION +++ b/VERSION @@ -89,5 +89,5 @@ IPA_DATA_VERSION=20100614120000 # # ######################################################## IPA_API_VERSION_MAJOR=2 -IPA_API_VERSION_MINOR=75 -# Last change: npmccallum - HOTP support +IPA_API_VERSION_MINOR=76 +# Last change: npmccallum - otptoken defaults change -- cgit