[#2083] bugfix: added Shiro core additional ClassLoader to be used when seria…#2085
Conversation
…lizing / deserializing Principals for remember me
|
Heh... I vaguely seem to remember suggesting something like this last year, before you came up with the TCCL workaround mentioned here #1500 (comment) ...? 😄 Nice and understandable! I like! Initially LGTM, but I will test the branch on my apps and report back. |
You did. Sorry about that. I guess I was too busy to comprehend what you were truly suggesting at the time, there was a lot going on then :) Well better late than never. |
|
I have tested the branch with the apps in myapps and can confirm that everything seems to work normally in a smoke test and no stack traces appeared in the log. For reference, here is what I did to rebuild:
(lots of stuff but except for bumping the versions the computer did most of the work) |
|
@fpapon waiting for your approval. Thanks. |
…lizing / deserializing Principals for remember me
fixes #2083
supersedes #2084
Following this checklist to help us incorporate your contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a GitHub issue. Your pull request should address just this issue, without pulling in other changes.
[#XXX] - Fixes bug in SessionManager,where you replace
#XXXwith the appropriate GitHub issue. Best practiceis to use the GitHub issue title in the pull request title and in the first line of the commit message.
fixes #XXXif merging the PR should close a related issue.mvn verifyto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.git rebase -i.Trivial changes like typos do not require a GitHub issue (javadoc, comments...).
In this case, just format the pull request title like
[DOC] - Add javadoc in SessionManager.If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.