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 <jcholast@redhat.com>
This commit is contained in:
Nathaniel McCallum
2014-02-20 13:21:32 -05:00
committed by Petr Viktorin
parent 561e57d121
commit 21ff4f920e
3 changed files with 58 additions and 57 deletions

View File

@@ -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