[seam-dev] [Security] Issues with JpaIdentityStore

Hi, This is my first message here, so is's perfect moment to say "Hello Everybody!". I'm a developer from Poland and big fan of Seam, starting from v2.1 :) Few weeks ago I built simple SeamSecurity client app based on idm-console example. I created very simple maven module (let's call it "core" for convenience) with identity-related entities which is used by customized idm-console project. (Almost) everything was fine with 3.0.0.Final, but yesterday I switched to 3.1.0.Beta3 and found the following issues: 1) Entities don't get configured via XML anymore. Maybe it is connected with the next point, I cannot say because haven't tried XML configuration after renaming seam-beans.xml. 2) Annotation based configuration for identity entities doesn't work if my "core" dependency contains META-INF/seam-beans.xml. Works fine after renaming it to beans.xml. 3) IdentityObjectRelationship entity name is hardcoded in string queries :) I guess it will be fixed in next Beta. Or should I create Jira issue for this? I have also one additional question: 4) PasswordHash utility is still not used anywhere, nor the PasswordCredential.getEncodedValue() utiliy. What are the plans for hashing support? In Seam 2.x this feature was working very fine and was very useful. Anyway, thanks for this Beta3 version. I hope Seurity will be fully operational soon :) -- Best regards, Michal Kaplon ---------------------------------------------------------------- Najtansze auta w Internecie! http://linkint.pl/f2a5a