Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-1290

Domain Join - IDM: Backend Service

    • DJ-IDM: Backend Service
    • 0% To Do, 0% In Progress, 100% Done
    • False

      Goal:

      • Provide the necessary API service endpoints for managing the domain blueprints for a given organization, according to console.dot standards.

      Assumptions:

      • Customer has IDM deployment.
      • CRC user has administrator access to IDM domain.
      • Customer will
      • (Maybe) CRC user has root access to IDM server.

      Acceptance Criteria:

      • An architecture diagram for the service is provided.
      • A design of the API is provided.
      • A data model for the database is provided.
      • CRUD operations for a "blueprint" (aka 'domains' internally) are implemented and unit tests to cover them.
      • It follows the console.dot platform standards.

      Open questions:

      • I would add as additional epics:
        • The operations are authorized based on RBAC service of the platform (permissions and roles TBD).
          • which permissions and role we want? they are named: <service>:<resource>:<verb>
        • The service expose metrics (metrics TBD)
          • which metrics want to be retrieved?
            • http status counter?
            • latency?
            • custom metrics?
        • ConsoleDot UI?

            Unassigned Unassigned
            avisiedo@redhat.com Alejandro Visiedo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: