Uploaded image for project: 'Seam Security'
  1. Seam Security
  2. SEAMSECURITY-142

Support JPA identity store user and group config separately (without requiring a common identity type table)

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      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

        <plidm:JpaIdentityStoreConfiguration>
          <plidm:userClass>com.company.project.model.???</plidm:userClass>
          <plidm:groupClass>com.company.project.model.???</plidm:groupClass>
          ...
      

      This is a blocker for most of my webapps, because I often cannot change the data model.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            kwutzke Ka Wu (Inactive)
            Archiver:
            samahaja Sagar Mahajan

              Dates

              Created:
              Updated:
              Archived: