Jenkins build is back to stable : Roller » Roller Webapp #1146

See

Jenkins build is back to stable : Roller #1146

See

Jenkins build became unstable: Roller » Roller Webapp #1145

See

Jenkins build became unstable: Roller #1145

See

Re: Spring password encoder depreciated

For your below suggestion, I'm not sure how the code can go from an explicit MD5 or SHA encoder to a generic StandardPasswordEncoder() and still work. I think your solution is OK otherwise. Another solution I'm thinking of is adding a new column "BCPassword" or whatever to the Roller User tab

Re: Spring password encoder depreciated

Gen, PasswordEncoder has been depreciated for some time now, but whether it will be removed I am unsure. If passwords have been hashed its never going to be an easy change as its a one way encryption. The changes if I remember are mainly in the java classes so we could leave the old code and use

Re: Spring password encoder depreciated

If this configuration is done in XML: http://mprabhat.wordpress.com/2012/07/20/spring-security-3-1-password-encoder-with-custom-database-and-jsf-2-0/, it may be sufficient to provide two XML blocks, one using the deprecated and one using the new, with the deprecated one commented-out. Then the

Re: Spring password encoder depreciated

If we have to, we have to--but how will people be able to upgrade from 5.0.x to 5.1 without everyone's password being lost and hence locked out (i.e., if blogs.oracle.com tried this all users would be locked out, right?) Perhaps we can support both algorithms in 5.1 (http://stackoverflow.com/a

Spring password encoder depreciated

Gentlemen, The class org.springframework.security.authentication.encoding.PasswordEncoder SHA and MD5 in RollerContext has been depreciated, it can be replaced by StandardPasswordEncoder(), BCryptPasswordEncoder() and NoOpPasswordEncoder. The down side is the encryption is based on the username a

Jenkins build is back to stable : Roller » Roller Webapp #1144

See

Jenkins build is back to stable : Roller #1144

See