OAuth2 token persistence in the Tonr application

[k0k0pelli]

We have pulled the sparklr and tonr applications and then deploayed them on a local server. The first pass goes fine:

• login to tonr
• click on sparklr link
• login to tonr
• authorize tonr from sparklr

And everything goes as expected. If we completely close the browser session (leaving the application server running) the tonr application asks the user to reauthenticate, though the authorization server side is preserved.

Why is the sparklr application requestng authentication in the new browser session?

[Dave Syer]

Sparklr stores authentication information (but not access tokens or user approvals) in a normal session governed by a browser cookie. If the broser doesn't send the cookie it will prompt for authentication, just like any Spring Security application.

I think your third bullet is "login to sparklr"?