Details

      Description

      Create REST APIs for appropriate enrollment functionality.

      This includes managing petitions and support for reconciliation.

      This does NOT include management flow configurations, as those are specifically intended to configure the UI and so (at least for now) do not need to be exposed via REST.

        Issue Links

          Activity

          Hide
          Benn Oshrin added a comment -
          See also CO-182 for potential REST needs.
          Show
          Benn Oshrin added a comment - See also CO-182 for potential REST needs.
          Hide
          Benn Oshrin added a comment -
          Initial requirements for 0.5 are probably limited to real time reconciliation.
          Show
          Benn Oshrin added a comment - Initial requirements for 0.5 are probably limited to real time reconciliation.
          Hide
          Benn Oshrin added a comment -
          The currently enrollment flow UI implementation is done using the existing View model, and isn't relying on the REST API, even for AJAXy stuff.
          Show
          Benn Oshrin added a comment - The currently enrollment flow UI implementation is done using the existing View model, and isn't relying on the REST API, even for AJAXy stuff.

            People

            • Assignee:
              Scott Koranda
              Reporter:
              Benn Oshrin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: