Uninitialized Constant in Password Flow about doorkeeper

[felipeelias]

Couldn't reproduce. Just tested against ruby 1.8/1.9 and Rails 3.2.5 and doorkeeper 0.4.1

Is anyone else having this issue?

[jfrey]

I had some more time to look at this today and it appears to be working after a reinstall of the gem so perhaps an issue with my RVM or the initial install.

Apologies for the false alarm / inconvenience.

[jfrey]

Actually this is occurring when I specify a scope in my request. If I leave the scope blank it passes through correctly.

curl -i http://localhost:3000/oauth/token \
  -F grant_type=password \
  -F client_id=id \
  -F client_secret=secret \
  -F "scope=" \
  -F [email protected] \
  -F password=password

If I leave scope out or set it to scope= then it works as expected. When I set scope=public it fails. In my initializer I uncommented the default_scopes line.

Edit: I verified this in master as well.

[felipeelias]

Ok. Makes sense. I'll investigate.

Thanks for taking your time debugging it.

[felipeelias]

Can you test this branch please? https://github.com/applicake/doorkeeper/tree/password-scopes-fix

[jfrey]

Looks good, could your merge this into master as well?

[felipeelias]

Yes, I'll update this today and release 0.4.2 version

[jfrey]

Great thanks!

[felipeelias]

released 0.4.2 and updated master.