Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-1992

Provide an example configuration that shows how to enable security for remote EJBs

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2018.5.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      20

      Description

      We now have remote EJBs in product. However, the default configuration we inherit from community disables all security by default. Specifically, the Remoting connector we expose doesn't configure a security realm. I.e., it's open to the world by default. That sounds like a recipe for disaster.

      I know that, unlike WildFly, we can't easily configure security realms by default (because we can't point to pre-existing .properties files), but it's pretty easy to configure a security realm in project-defaults.yml, and if the user wants to expose remote EJBs, they should also configure some security.

      Thoughts?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  heiko.braun Heiko Braun
                  Reporter:
                  lthon Ladislav Thon
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: