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

idmsvc-backend: include org_id in registration token

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • Identity Management
    • None
    • IdM Insights CY25Q1
    • 3
    • None

      • Include org id in registration token so that we can detect and report registration failure due to IPA server org not matching ConsoleDot org that generated the token.  See notes(important & urgent)
      • It can happen in scenarios with multiple accounts (i.e. Sales people trying to demo it to clients). The mismatch will occur and the UI is not friendly enough to guide which kind of error it is. Improving the message can lead people to have a better experience and not suffer figuring it out by themselves.
      • PHASE 1 - backend: include org_id in registration token (THIS TICKET)
      • PHASE 2a - ipa-hcc-server: update to check the org-id from the (updated) token format against the RHEL machine's subscription (org membership). ( https://issues.redhat.com/browse/HMS-5628 )
      • PHASE 2b - backend: verify org_id in registration token.  Return a distinct error response with more useful error message when token org_id does not match client org_id (https://issues.redhat.com/browse/HMS-5627) .

              Unassigned Unassigned
              ftweedal@redhat.com Fraser Tweedale
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: