accept token generated through sso-login from a cookie

Description

The cookie name could be e.g ssoToken. This would be used in conjuction with redirects issues by the SSO module and will also hide the token from the URL.

Environment

None

Potential Workaround

None

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Mike TaylorJuly 28, 2017 at 5:09 PM

(I've sent this straight to CLOSED, rather than IN REVIEW, since the proof of it will come when third-party developers integrate with this functionality rather than by Cate or Charlotte verifying the some user-facing function works.)

Mike TaylorJuly 28, 2017 at 5:08 PM

Fixed in https://github.com/folio-org/stripes-core/commit/db4f46f14d945bf6637f7d12c5d71483b138633b

To test:
1. Log into Stripes.
2. Go to Settings > Developer > Set Token.
3. Copy the current session's token from the textbox.
4. Log out
5. Use your browser's development tools to manually create a cookie for your Stripes server, with name setToken and with the value you copied in step 3.
6. Go directly to your Stripes service's /sso-landing page.

You will now be logged in once more, to the previous session.

Done

Details

Assignee

Reporter

Priority

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 20, 2017 at 11:38 AM
Updated July 28, 2017 at 5:09 PM
Resolved July 28, 2017 at 5:09 PM
TestRail: Cases
TestRail: Runs