register with an Identity Provider based on one time password

This bug was originally filed in Launchpad as [LP: #1245913](https://bugs.launchpad.net/cloud-init/+bug/1245913)

Launchpad details

affected_projects = []

assignee = ayoung

assignee_name = Adam Young

date_closed = None

date_created = 2013-10-29T14:59:39.367313+00:00

date_fix_committed = None

date_fix_released = None

id = 1245913

importance = low

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1245913

milestone = None

owner = ayoung

owner_name = Adam Young

private = False

status = triaged

submitter = ayoung

submitter_name = Adam Young

tags = []

duplicates = []

_Launchpad user **Adam Young(ayoung)** wrote on 2013-10-29T14:59:39.367313+00:00_

When launching a virtual machine, the baseline access method used by most infrastructure is to copy a public key onto the vm in a known location. This has several shortcomings:

1. Keys have no expiration or revocation
2. Keys are specific to a user, providing no way top perform group operations

A preferred approach is to register the machine with a centralized authenitation source, such as FreeIPA.

While it is possible to perform the registration in two steps, therei s a naming issue involved that makes it difficult to perform.

Inseat, we want to be able to specify a new key for a one time password, or OTP. For FreeIPA, the goal is to do something like

ipa-client-install ${otp}

during the cloud-init process, without taking over all of cloud-init.

This bug is for the feature. We will continue to drive the design in the comments.