Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-497

Improve DeploymentSupport setting on a realm

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Invalid
    • Affects Version/s: 1.0-M4
    • Fix Version/s: None
    • Component/s: security
    • Labels:
      None

      Description

      The GenericSecurityRealm currently provides DeploymentSupport features if the login modules implement DeploymentSupport. It would be nice to support an external DeploymentSupport, set as a property on the GenericSecurityRealm. Currently that ability is there (on DS per login domain for the realm), but it just expects to get a class name, and this doesn't really work as the DeploymentSupport instance has no way of being configured (e.g. to point to a specific DB, LDAP server, etc.). Probably, a DeploymentSupport defined separately from the realm should be instantiated and configured as a GBean, and the realm given the ObjectName instead of the class name. However, I'm not 100% convinced that "GBean creep" is the way to go here. We could also add the same initialize method declared in LoginModule to DeploymentSupport, and then provide a way to send Options to the DeploymentSupport on the realm, but that seems pretty complex too.

        Attachments

          Activity

            People

            • Assignee:
              ammulder Aaron Mulder
              Reporter:
              ammulder Aaron Mulder
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: