Npmccallum (talk | contribs) |
Npmccallum (talk | contribs) |
||
| Line 15: | Line 15: | ||
Until recently, no two-factor authentication was possible with Kerberos. However, the standardization of RFC 6560 combined with recent work in the MIT krb5 code makes it possible to now offer support for two-factor authentication in Kerberos. | Until recently, no two-factor authentication was possible with Kerberos. However, the standardization of RFC 6560 combined with recent work in the MIT krb5 code makes it possible to now offer support for two-factor authentication in Kerberos. | ||
Fedora 18 already supports the client side of this proposal. FreeIPA will be landing support for the server side in Fedora 19. | Fedora 18 already supports most of the client side of this proposal. FreeIPA will be landing support for the server side in Fedora 19. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Revision as of 16:34, 29 January 2013
FreeIPA Two Factor Authentication
Summary
Provide Kerberos enabled, LDAP replicated, two-factor authentication for FreeIPA.
Owner
- Name: Nathaniel McCallum
- Email: npmccallum@redhat.com
Current status
- Targeted release: Fedora 19
- Last updated: 2013-01-29
- Percentage of completion: 60%
Detailed Description
Until recently, no two-factor authentication was possible with Kerberos. However, the standardization of RFC 6560 combined with recent work in the MIT krb5 code makes it possible to now offer support for two-factor authentication in Kerberos.
Fedora 18 already supports most of the client side of this proposal. FreeIPA will be landing support for the server side in Fedora 19.
Benefit to Fedora
Users of FreeIPA will be able to deploy two-factor authentication across the replicated user directory.
Scope
- sssd will need to merge a patch for client side integration with OTP (already written).
- krb5 will need to backport a self-contained plugin for the server-side support (upstream work in process).
- FreeIPA will gain a dependency on libverto (already packaged and already a dependency of krb5).
How To Test
Each component will have unit tests.
To test the feature as a whole, you will need a TOTP (RFC 6238) client, such as Google Authenticator. You will then add a token to a user and confirm that authentication succeeds.
User Experience
No change will be made by default. When an admin configures a user for two-factor authentication, the authenticating user will need to use a TOTP client.
Dependencies
MIT needs to merge the OTPOverRADIUS proposal upstream. However, since we are backporting this feature anyway, this risk is minimal.
Contingency Plan
None necessary, FreeIPA will work exactly like it currently does.
Documentation
Release Notes
None needed.