Uploaded image for project: 'COmanage'
  1. COmanage
  2. CO-1413

Org Identity Sync / Pipeline Processing Should Trigger Expiration Policies

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • COmanage Registry Future
    • COmanage Registry 2.0.0 (Passing Fad)
    • Registry
    • None

    Description

      It's possible that an Org Identity Sync / Pipeline could pull and create a record that is subject to immediate processing as determined by Expiration Policies (and, in the future, Activation Policies). An appropriate step should be added to Pipeline processing ("Evaluate Expiration Policies" Sync Strategy configuration?) to allow for this.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. CO-964 "Activation" Policies

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFM-61 Expiration Policies

          • Blocker - Blocks development and/or testing work, production could not run.
          • To Do

          Improvement - An improvement or enhancement to an existing feature or task. CO-1398 Improve Handling of CO Pipeline Role Status Sync

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              benn.oshrin@at.internet2.edu Benn Oshrin (internet2.edu)
              benn.oshrin@at.internet2.edu Benn Oshrin (internet2.edu)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: