Sorry, posted too much info. Yes this has nothing to do with salting, but having grabbed the latest source whee Les posted the changes and it resulted in the JSESSION cookie: JSESSIONID=61112b06-04f5-4e7c-af87-b84c3901d4af; Path=/service; Max-Age=-1; which is causing it to be deleted by the browser. I can create a JIRA for this, but was not sure if this is intentional for 1.1-SNAPSHOT -- View this message in context: http://shiro-developer.582600.n2.nabble.com/Password-hashing-getting-the-salt-from-AuthenticationInfo-tp5653460p5660714.html Sent from the Shiro Developer mailing list archive at Nabble.com.
- Password hashing - getting the salt from AuthenticationInf... Les Hazlewood
- Re: Password hashing - getting the salt from Authenti... Kalle Korhonen
- Re: Password hashing - getting the salt from Auth... Les Hazlewood
- Re: Password hashing - getting the salt from ... Mike K
- Re: Password hashing - getting the salt f... Les Hazlewood
- Re: Password hashing - getting the s... Les Hazlewood
- Re: Password hashing - getting t... Mike K
- Re: Password hashing - getti... Kalle Korhonen
- Re: Password hashing - getti... Mike K
- Re: Password hashing - getti... Kalle Korhonen
- Re: Password hashing - getti... Les Hazlewood
- Re: Password hashing - getting the salt from Authenti... Alan D. Cabrera
- Re: Password hashing - getting the salt from Auth... Kalle Korhonen
- Re: Password hashing - getting the salt from ... Alan D. Cabrera
- Re: Password hashing - getting the salt from Auth... Les Hazlewood
- Re: Password hashing - getting the salt from ... Alan D. Cabrera
- Re: Password hashing - getting the salt f... Les Hazlewood
- Re: Password hashing - getting the s... Les Hazlewood
- Re: Password hashing - getting t... Alan D. Cabrera
