problems logging in /admin about oauthd

[bumpmann]

It should have remembered the first time you login... I just push a script to reset the password, just type node ./tools/login_reset.js in the oauthd folder.

If you have more infos about where the login fails, please tell us

You can also run npm test to check your environment

If you update oauthd with git pull without reinstall, you should recompile with npm run install or grunt

[joliveros]

Ok wow. I was so lost. Thanks for that.

On 12/11/2013 11:00 AM, bumpmann wrote:

It should have remembered the first time you login... I just push a
script to reset the password, just type |node ./tools/login_reset.js|
in the oauthd folder.

If you have more infos about where the login fails, please tell us

—
Reply to this email directly or view it on GitHub
#32 (comment).

[joliveros]

After I run that file I get a confirmation the credentials were reset.
However, when I try to login again with new credentials it fails. :(

On 12/11/2013 08:32 PM, Jose Oliveros wrote:

Ok wow. I was so lost. Thanks for that.

On 12/11/2013 11:00 AM, bumpmann wrote:

It should have remembered the first time you login... I just push a
script to reset the password, just type |node ./tools/login_reset.js|
in the oauthd folder.

If you have more infos about where the login fails, please tell us

—
Reply to this email directly or view it on GitHub
#32 (comment).

[bumpmann]

Does it works with npm test ?

[joliveros]

I get : 'Done, without errors.'

On 12/17/2013 03:39 PM, bumpmann wrote:

Does it works with |npm test| ?

—
Reply to this email directly or view it on GitHub
#32 (comment).

[mojotalantikite]

I was having the same issues in Chrome (v 31.0.1650.63), but it seems to work fine in Firefox and Safari.

[stanhu]

The problem was in the format of the Set-Cookie response header. For example, this is what showed up on my Chrome browser:

Set-Cookie: accessToken=%223eacnaMBbsbqm23klZcM1bv4CbA%22; Path=/; Expires=Fri Jan 17 2014 17:19:55 GMT-0800 (PST)

Per RFC 6265 5.1.1 (http://tools.ietf.org/search/rfc6265#section-5.1.1) the time zone field should be simply be in UTC/GMT time. For example, this works in Chrome:

Set-Cookie: accessToken=%223eacnaMBbsbqm23klZcM1bv4CbA%22; Path=/; Expires=Fri Jan 17 2014 17:19:55 GMT

I fixed the problem and sent a pull request.