Open Password Automation Recipe (OPAR) Protocol
draft-bwilliams-kitten-opar-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Branden Williams | ||
| Last updated | 2018-04-19 (latest revision 2017-09-26) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-bwilliams-kitten-opar-00.txt
Abstract
This document introduces the Open Password Automation Recipe (OPAR) Protocol, a suggested format for providing instructions to password managers programmatically that defines the valid construction of a password. With password managers becoming integrated into browsers, websites should be able to describe the elements of an acceptable password programmatically so password management plugins can read and automatically generate the best option. Without this, manual intervention by the user is required when the password is too long, contains invalid characters, or does not meet complexity requirements.
Authors
Branden Williams (ietf@brandenwilliams.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)