Summary
We store the risk score in SessionManager. But the session data isn't reconstructed when a job autocreates a local account. If we set the risk score in a short-lived global memcache key (using the username as part of the key), then we should be able to try the SessionManager, and then fall back to the memcache value when retrieving the score, and be able to have access to the score in wikis where an account is autocreated via a job.
Acceptance criteria
- The risk score is accessible in wikis where the account is autocreated