Yes I already fixed the problem. Anyhow thank you for your help and suggested code. I would like to know whether is it possible to use the Bcrypt hashing algorithm instead of SHA-512.
alarinn wrote > > Have you made the necessary changes to the realm? > > For example, here's my setup: > > * <bean id="sha512Matcher" > class="org.apache.shiro.authc.credential.HashedCredentialsMatcher"> > > <property name="hashAlgorithmName" value="SHA-256" /> > <property name="hashIterations" value="1024" /> > </bean>* > > > > <bean id="opacsRealm" class="org.apache.shiro.realm.jdbc.JdbcRealm"> > <property name="dataSource" ref="dataSource" /> > <property name="authenticationQuery" > value="select PASSWORD, SALT from SEC_USERS where NAME > = ?" /> > <property name="userRolesQuery" > value="SELECT ROLE_NAME FROM SEC_USERS_ROLES WHERE > USER_NAME = ?" /> > <property name="permissionsQuery" > value="SELECT permission FROM SEC_ROLES_PERMISSIONS > WHERE ROLE_NAME = > ?" /> > <property name="permissionsLookupEnabled" value="true" /> > * <property name="saltStyle" value="COLUMN" /> > <property name="credentialsMatcher" ref="sha512Matcher"/>* > </bean> > > You may or may not need the saltStyle property but you do need the > hashAlgorithmName and hashIterations defined in your > HashedCredentialsMatcher bean definition. > -- View this message in context: http://shiro-user.582556.n2.nabble.com/Salting-password-tp7577622p7577697.html Sent from the Shiro User mailing list archive at Nabble.com.
