ipa client allows invalid otptoken validity timespan, eg 20140402000000Z - 20140101000000Z
[x@y tmp]$ ipa otptoken-mod d3cd7d31-d273-4061-bf72-f4ca1f0affb7 --not-before="20140402000000Z" --not-after="20140101000000Z" --------------------------------------------------------- Modified OTP token "d3cd7d31-d273-4061-bf72-f4ca1f0affb7" --------------------------------------------------------- Unique ID: de0a6fb7-628f-44ba-bcf4-429d51f317c5 Description: z Disabled state: FALSE Validity start: 20140402000000Z Validity end: 20140101000000Z Vendor: FreeIPA Model: totp
Moving stabilization tickets that do not affect FreeIPA 4.0 release usability in any significant way to 4.0.1 stabilization milestone.
attachment freeipa-dkupka-0005-Verify-otptoken-timespan-is-valid.patch
attachment freeipa-dkupka-0005-2-Verify-otptoken-timespan-is-valid.patch
FreeIPA 4.0.1 was released, moving to next bugfixing release milestone.
attachment freeipa-dkupka-0005-3-Verify-otptoken-timespan-is-valid.patch
master:
ipa-4-1:
ipa-4-0:
Metadata Update from @amisnyov: - Issue assigned to dkupka - Issue set to the milestone: FreeIPA 4.0.2
Login to comment on this ticket.