These are chat archives for alvarosanchez/spring-security-rest

8th
Apr 2015
Álvaro Sánchez-Mariscal
@alvarosanchez
Apr 08 2015 11:14
@jadelus the initial design didn't consider the need to lookup for existing tokens generated, because the initial implementation (Memcached) you can get the user details given the token, but not the other way around
It could be solved by handling reverse lookup entries, so the token storage stores both directions at the same time
in Grails cache, the implementation would be similar
and in GORM, is easily solvable too
however, in JWT, as there is no real state not storage at all, there is no way to solve it
I don't see a major issue generating a token every time, as they will expire anyway
Álvaro Sánchez-Mariscal
@alvarosanchez
Apr 08 2015 11:24
@dogramacigokhan all you have to do is to register your own implementation of an AuthenticationFailureHandler in resources.groovy with the bean name restAuthenticationFailureHandler
Sufyan Shoaib
@sufyanshoaib
Apr 08 2015 12:53
I have having logout issue with rest plugin, i have posted my question here: http://stackoverflow.com/questions/29514288/logout-api-error-rest-spring-security-plugin-in-grails @alvarosanchez .. any idea?
Álvaro Sánchez-Mariscal
@alvarosanchez
Apr 08 2015 14:07
@sufyanshoaib answered you on SO
jadelus
@jadelus
Apr 08 2015 14:29
@alvarosanchez thank you for the clarification.
Sufyan Shoaib
@sufyanshoaib
Apr 08 2015 14:31
@alvarosanchez thanks for the reply, but issue is i have java 6, with which it wont work.. giving unable to resolve class java.nio.charset.StandardCharsets error
Álvaro Sánchez-Mariscal
@alvarosanchez
Apr 08 2015 14:32
@sufyanshoaib there is no significant version changes between 1.4.0 and 1.4.1. Could you please run grails clean-all && grails compile?