Changes/IPAv3OTPUI

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Created page with "= FreeIPA OTP UI = == Summary == FreeIPA will gain a user interface for managing users' OTP tokens. == Owner == * Name: Nathaniel McCallum * Email: npmcc...")
 
(Scope details based on the page)
Line 34: Line 34:
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
* Proposal owners: npmccallum
+
* Proposal owners: change development
 
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  

Revision as of 11:46, 16 July 2013

Contents

FreeIPA OTP UI

Summary

FreeIPA will gain a user interface for managing users' OTP tokens.

Owner

Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-07-15
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

In Fedora 19 we introduced rudimentary support for OTP in krb5 and FreeIPA. Building on this work, we are creating a management system so that tokens can be managed alongside other user attributes.

Benefit to Fedora

Support for fully replicated two factor authentication.

Scope

  • Proposal owners: change development
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)

Release Notes