Karsten Wutzke created SEAMSECURITY-142: ------------------------------------------- Summary: Support JPA identity store user and group config separately (without requiring a common identity type table) Key: SEAMSECURITY-142 URL: https://issues.jboss.org/browse/SEAMSECURITY-142 Project: Seam Security Issue Type: Feature Request Reporter: Karsten Wutzke Priority: Blocker Currently the JpaIdentityStore has a common configuration for Users and Groups. However, there are some problems with this: Seam 3 Security requires a common entity for users and groups, which doesn't generally make sense. In some DBs users and groups have been split up into separate tables, which makes Seam 3 Security kind of intrusive to the data model, which might not be changable at all. It would be very useful to be able to configure the users and groups table independently/separately, e.g. via an option {code} <plidm:JpaIdentityStoreConfiguration> <plidm:userClass>com.company.project.model.???</plidm:userClass> <plidm:groupClass>com.company.project.model.???</plidm:groupClass> ... {code} This is a blocker for most of my webapps, because I often cannot change the data model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira