Opened 12 years ago
Closed 11 years ago
#257 closed design (fixed)
Considerations for new authentications schemes
| Reported by: | mnot@… | Owned by: | julian.reschke@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 16 |
| Component: | p7-auth | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
We need to document what HTTP-specific things that new authentication schemes need to consider.
Attachments (1)
Change History (7)
comment:1 Changed 11 years ago by julian.reschke@…
- Owner set to julian.reschke@…
- realm not required but reserved
- Authorization is required
- link to Part 1 with respect to "2.2 Message Orientation and Buffering"
comment:2 Changed 11 years ago by julian.reschke@…
comment:3 Changed 11 years ago by julian.reschke@…
- Milestone changed from unassigned to 16
- Resolution set to incorporated
- Status changed from new to closed
comment:4 Changed 11 years ago by julian.reschke@…
comment:5 Changed 11 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:6 Changed 11 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)