I ended up implementing an AuthenticatingFilter which, after a
successful login, sends back an access token.
And an AuthorizingFilter which looks for the presence of a valid access
token in a certain http header.
Sorry for the low effort question.
On 13-Oct-16 09:19, Gabriel Titerlea wrote:
H
The original developer (Lez Hazelwood) went with what he knew best, which was
the Spring Framework which uses JSP pages as far as I know for web
development. But as long as the resulting HTTP request is the same it does
not matter whether that request was generated by JSP, naked HTML5, node.js,
Pyt
It is not the Subject, but the SecurityManager which is based on the machine.
So, the result of subject.isAuthenticated() on one machine can differ from
subject.isAuthenticated() on another machine even for the same instance of
'subject'.
What 'getSubject' returns is entirely dependent on your con
I'm itching to create a new release of my application with the recent pull
requests.
I'm taking out Spring Security and replacing it with Shiro!
Is there a plan for a new point release soon?
Are they done ad-hoc or on a monthly basis or something?
Thanks
--
View this message in context:
http:
>The original developer (Lez Hazelwood) went with what he knew best, which was
the Spring Framework which uses JSP pages as far as I know for web
development. But as long as the resulting HTTP request is the same it does
not matter whether that request was generated by JSP, naked HTML5, node.js,
Py
I'm not sure why that last message sent when I was adjusting font size...
I guess these double emails continue
>It is not the Subject, but the SecurityManager which is based on the machine.
So, the result of subject.isAuthenticated() on one machine can differ from
subject.isAuthenticated
