Issues (76–88 of 88)

Title	T	P	Status	Assignee	Created	Updated
#60: Only one method to Token Bind AT rather than two? FAPI 1: Advanced	task	critical	closed		2017-01-16	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
#72: Spec not clear as to which auth flows are supported FAPI 1: Advanced	proposal	major	closed		2017-03-02	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
#79: Part 1: issues with x-fapi-customer-last-logged-time header FAPI 1: Baseline	bug	major	closed		2017-03-22	2017-04-06
#73: Spec says Authorization Server shall support both public and confidential clients; FAPI 1: Advanced	bug	major	closed		2017-03-02	2017-03-29
#63: There is no qualification on x-fapi-customer-id FAPI 1: Baseline	bug	major	closed	Nat Sakimura	2017-01-30	2017-02-03
#69: Notes like this are strange “NOTE: Providing access to Javascript clients or not has different security properites.;” FAPI 1: Baseline	bug	major	closed	Sascha Preibisch	2017-01-31	2017-02-02