|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Bruno,
I have cloned your application's repository and I'm using the 'sec-update' branch to simulate this issue.
During my tests I noticed two things:
1) You're using a SalesAgent which is a sub-type of Agent. Wondering if you can provide a specific @Entity to map this custom type, given that it have some specific properties that should also be mapped.
2) The issue is happening because there is no entity that defines a @IdentityManaged annotation for your custom type. When trying to create the custom type, the JPA store fails some times (in a very random behavior).
Today, custom identity types should be mapped like this:
org.picketlink.test.idm.basic.CustomAccountTestCase
I have changed the JPA store to also support custom types that does not define their own entity classes. And added some validations to the JPA store to avoid the random behavior when creating types like what you're proposing.
Also, I have a working version of your application now running. And I hit a ClassCastException on aerogear-security-picketlink because the SalesAgent is not an User, but an Agent.
Thanks.
Pedro Igor