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

Legacy subsystem jacorb's migrate() op should migrate to elytron

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 28.0.0.Final
    • None
    • IIOP, Migration
    • None

    Description

      Currently the migrate() op is migrating the legacy jacorb configuration to an iiop configuration which requires the legacy security realm framework, no longer supported.

      I believe that at least any usage of security=identity should be migrated to security=elytron.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24739 Legacy subsystem jacorb's migrate() op should migrate to elytron

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is triggering

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17893 Jacorb subsystem migrate operation does not include a migration warn if the 'client' or 'identity' security were used

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              emartins@redhat.com Eduardo Martins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: