Old Yubikey-specific code and settings need to be removed
Bug #928346 reported by
Stuart Metcalfe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Confirmed
|
Low
|
Unassigned |
Bug Description
The old, experimental, Yubikey code and settings are still lurking in at least the schema.py and main.cfg files in both trunk and the sso-config branch. We can't remove the section independently as it's defined as 'fatal=True' so we'll need to correlate removal and and deployment. There may also be removable Yubi code in other areas and in the templates. This has all been superseded by the OATH 2-factor code so should be removed at some point.
tags: | added: twofactor |
To post a comment you must log in.
How are you going to support multiple devices?
Yubikey supports sending token id, OATH by itself does not.