Identity/Features/Web-based Verified Email Client: Difference between revisions

Jump to navigation Jump to search
Line 41: Line 41:
| style="background-color: #efefef;"| '''Bug'''
| style="background-color: #efefef;"| '''Bug'''
| style="background-color: #efefef;"| '''Status'''
| style="background-color: #efefef;"| '''Status'''
|-
| Core VEP client implementation (can handshake w/ server register an email, generate keys, receive a cert, generate assertion;  no UI, no cert refresh) || - || -
|-
| Relying party wrapper implementation (can handle getVerifiedEmail call and interact w/ core VEP client in a popup window; still no UI nor cert refresh) || - || -
|-
| UI interaction through account creation / login / release of one email address (most UI will be generated by the server) || - || -
|-
| Email selection UI (mostly generated by UA) and integration into VEP process || - || -
|-
| Certificate refresh, successful only || - || -
|-
| Certificate refresh w/ failure || - || -
|-
| ============= OLDER (OBSOLETE?) MILESTONES BELOW =============
|-
|-
| Relying party API || - || -
| Relying party API || - || -
Line 47: Line 61:
|-
|-
| Email disclosure pop-up || - || -
| Email disclosure pop-up || - || -
|-
|-
| Email verification pop-up || - || -
| Email verification pop-up || - || -
25

edits

Navigation menu