Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17042

elytron-enabled defaults to false in datasources subsystem

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Critical
    • None
    • 27.0.0.Alpha5
    • JCA
    • None
    • Hide
      We can't change the model now. In WFLY-17559 this field is going to be deprecated and documented as having no effect.
      Show
      We can't change the model now. In WFLY-17559 this field is going to be deprecated and documented as having no effect.
    • ---
    • ---

    Description

      "elytron-enabled" => {
          "type" => BOOLEAN, 
          "description" => "Enables Elytron security for handling authentication of connections. The Elytron authentication-context to be used will be current context if no context is specified (see authentication-context).",
          "expressions-allowed" => true,
          "required" => false,
          "nillable" => true,
          "default" => false,
          "access-constraints" => {"sensitive" => {"data-source-security" => {"type" => "datasources"}}},
          "access-type" => "read-write",
          "storage" => "configuration",
          "restart-required" => "all-services"
      }
      

      Legacy security has been removed and Elytron became the default security provider. The default value of elytron-enabled attribute should be true. Perhaps it would even make sense to completely remove this attribute from all JCA subsystems.

      Attachments

        Issue Links

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              msimka@redhat.com Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: