openid / fapi / issues

Title	T	P	Status	Assignee	Created	Updated
#91: Id mix up attack FAPI 1: Advanced	bug	major	resolved		2017-05-06	2017-05-28
#78: Malicious Endpoint Attack FAPI 1: Advanced	enhancement	minor	closed		2017-03-17	2017-05-28
#77: IdP Confusion Attack FAPI 1: Advanced	enhancement	minor	closed		2017-03-17	2017-05-28
#92: Put cipher suite recommendations in the security considerations FAPI 1: Advanced	bug	major	closed	Edmund Jay	2017-05-06	2017-05-28
#99: Part 2: TLS considerations section may be ambiguous FAPI 1: Advanced	bug	major	closed		2017-05-24	2017-05-25
#87: Need create request_uri endpoint in AS FAPI 1: Advanced	enhancement	major	closed		2017-05-01	2017-05-16
#97: "alg" MUST not be "none" FAPI 1: Advanced	bug	major	resolved		2017-05-16	2017-05-16
#72: Spec not clear as to which auth flows are supported FAPI 1: Advanced	proposal	major	closed		2017-03-02	2017-05-13
#88: Sender constraining the code FAPI 1: Advanced	bug	major	invalid		2017-05-03	2017-05-13
#89: s_hash needs to be defined more precisely FAPI 1: Advanced	bug	major	invalid		2017-05-03	2017-05-13
#93: Not clear why AS needs to support signed+encrypted ID Token FAPI 1: Advanced	bug	major	resolved		2017-05-06	2017-05-13
#84: RFC2616 is obsolete and references to it should be replaced with updated RFCs FAPI 1: Baseline	bug	major	closed		2017-04-12	2017-05-10
#75: Support other method of HoK than TOKB FAPI 1: Advanced	bug	major	closed	Nat Sakimura	2017-03-03	2017-05-10
#74: Write spec should only support confidential clients FAPI 1: Advanced	proposal	major	resolved		2017-03-02	2017-04-26
#83: Support for GET FAPI 1: Baseline	enhancement	trivial	resolved		2017-03-23	2017-04-25
#85: Make the bullets in the provisions numbered FAPI 1: Baseline	bug	major	resolved	Nat Sakimura	2017-04-13	2017-04-14
#79: Part 1: issues with x-fapi-customer-last-logged-time header FAPI 1: Baseline	bug	major	closed		2017-03-22	2017-04-06
#61: Fund availability API Part 5: Protected Resources - RW	task	major	on hold		2017-01-17	2017-04-04
#73: Spec says Authorization Server shall support both public and confidential clients; FAPI 1: Advanced	bug	major	closed		2017-03-02	2017-03-29
#76: meaning of 'can'? FAPI 1: Baseline	bug	minor	resolved		2017-03-14	2017-03-23
#71: (ed) The heading level of 6.2.3 is wrong FAPI 1: Baseline	bug	minor	resolved	Nat Sakimura	2017-02-03	2017-02-08
#63: There is no qualification on x-fapi-customer-id FAPI 1: Baseline	bug	major	closed	Nat Sakimura	2017-01-30	2017-02-03
#70: "User-agents" in 5.2.3 confusing. FAPI 1: Baseline	bug	major	resolved		2017-02-01	2017-02-02
#68: Privacy consideration should be talking about more specifics FAPI 1: Baseline	bug	major	resolved	Nat Sakimura	2017-01-31	2017-02-02
#66: CustomerId == sub == x-fapi-customer-id: Should standardize as sub FAPI 1: Baseline	bug	major	resolved	Nat Sakimura	2017-01-31	2017-02-02

#91: Id mix up attack

FAPI 1: Advanced

bug

major

resolved

2017-05-06

2017-05-28

#78: Malicious Endpoint Attack

FAPI 1: Advanced

enhancement

minor

closed

2017-03-17

2017-05-28

#77: IdP Confusion Attack

FAPI 1: Advanced

enhancement

minor

closed

2017-03-17

2017-05-28

#92: Put cipher suite recommendations in the security considerations

FAPI 1: Advanced

bug

major

closed

Edmund Jay

2017-05-06

2017-05-28

#99: Part 2: TLS considerations section may be ambiguous

FAPI 1: Advanced

bug

major

closed

2017-05-24

2017-05-25

#87: Need create request_uri endpoint in AS

FAPI 1: Advanced

enhancement

major

closed

2017-05-01

2017-05-16

#97: "alg" MUST not be "none"

FAPI 1: Advanced

bug

major

resolved

2017-05-16

#72: Spec not clear as to which auth flows are supported

FAPI 1: Advanced

proposal

major

closed

2017-03-02

2017-05-13

#88: Sender constraining the code

FAPI 1: Advanced

bug

major

invalid

2017-05-03

2017-05-13

#89: s_hash needs to be defined more precisely

FAPI 1: Advanced

bug

major

invalid

2017-05-03

2017-05-13

#93: Not clear why AS needs to support signed+encrypted ID Token

FAPI 1: Advanced

bug

major

resolved

2017-05-06

2017-05-13

#84: RFC2616 is obsolete and references to it should be replaced with updated RFCs

FAPI 1: Baseline

bug

major

closed

2017-04-12

2017-05-10

#75: Support other method of HoK than TOKB

FAPI 1: Advanced

bug

major

closed

Nat Sakimura

2017-03-03

2017-05-10

#74: Write spec should only support confidential clients

FAPI 1: Advanced

proposal

major

resolved

2017-03-02

2017-04-26

#83: Support for GET

FAPI 1: Baseline

enhancement

trivial

resolved

2017-03-23

2017-04-25

#85: Make the bullets in the provisions numbered

FAPI 1: Baseline

bug

major

resolved

Nat Sakimura

2017-04-13

2017-04-14

#79: Part 1: issues with x-fapi-customer-last-logged-time header

FAPI 1: Baseline

bug

major

closed

2017-03-22

2017-04-06

#61: Fund availability API

Part 5: Protected Resources - RW

task

major

on hold

2017-01-17

2017-04-04

#73: Spec says Authorization Server shall support both public and confidential clients;

FAPI 1: Advanced

bug

major

closed

2017-03-02

2017-03-29

#76: meaning of 'can'?

FAPI 1: Baseline

bug

minor

resolved

2017-03-14

2017-03-23

#71: (ed) The heading level of 6.2.3 is wrong

FAPI 1: Baseline

bug

minor

resolved

Nat Sakimura

2017-02-03

2017-02-08

#63: There is no qualification on x-fapi-customer-id

FAPI 1: Baseline

bug

major

closed

Nat Sakimura

2017-01-30

2017-02-03

#70: "User-agents" in 5.2.3 confusing.

FAPI 1: Baseline

bug

major

resolved

2017-02-01

2017-02-02

#68: Privacy consideration should be talking about more specifics

FAPI 1: Baseline

bug

major

resolved

Nat Sakimura

2017-01-31

2017-02-02

#66: CustomerId == sub == x-fapi-customer-id: Should standardize as sub

FAPI 1: Baseline

bug

major

resolved

Nat Sakimura

2017-01-31

2017-02-02

Issues

Issues (626–650 of 693)