openid / connect / issues / #8 - Messages - 3.1.3 response_type=none is not defined in OAuth — Bitbucket

Issue #8 resolved

Nat Sakimura created an issue 2011-08-16

It is an departure from OAuth 2.0.

Perhaps we should drop.

Comments (5)

hideki nara
- changed status to open
First of all, "response_type=none" must be described clearly. What use case is behind of this ?
- 2011-09-07T18:10:10+00:00
hideki nara
Through the ML discussion ( http://lists.openid.net/pipermail/openid-specs-ab/Week-of-Mon-20110905/000987.html ), spec writers will discuss about this on the upcoming Summit( Sept 2011 ) .
- 2011-09-07T23:10:50+00:00
Nat Sakimura reporter
"none" means response back to the client without any tokens nor code.
- 2011-09-15T02:34:58+00:00
Nat Sakimura reporter
- assigned issue to
  
  Nat Sakimura
It is probably clearer to state that only "state" SHOULD be returned.
- 2011-09-15T16:02:39+00:00
Nat Sakimura reporter
- changed status to resolved
fix #8 response_type=none returns only state

→ ba0797e86acf
- 2011-09-15T16:04:00+00:00
Log in to comment

Assignee: Nat Sakimura

Type: bug

Priority: major

Status: resolved

Component: –

Milestone: –

Version: –

Votes: 0

Watchers: 0

Jira Software: the preferred issue tracker for Bitbucket. Join the team!