Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Expired
    • Affects Version/s: 11.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Sprint:
      Sprint 81 - Sustaining
    • Support Ticket IDs:

      Description

      OpenAM should have a formalized patching mechanism to install and manage software patches. In this context, "patch" means an archive (typically a jar file) of java classes and other resources that replace or extend the contents of the OpenAM web application.

      Administrators would greatly benefit from the following features:

      • An easy way to install patches automatically; ideally this would be a section in the admin console where you can upload and enable patches
      • A new section in the admin console that shows a list of installed patches and their contents/description
      • An easy way to disable/remove installed patches
      • The ability to manage different versions of the same patch
      • A mechanism that prevents collisions, i.e. patches containing different versions of the same file overwriting each other - there should be a way to resolve conflicts (e.g. to choose which version should take precedence)

      Such a patching tool has to be container independent or accommodate various deployment scenarios and container specific requirements.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              zoltan.tarcsay Zoltan Tarcsay
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: