RootCauseunvalidated

Once pairing is done then user is authorized to call group api to see detail of that group. — external user will login via external application and paired with a group they belong to. Tension: external user is calling group api using same external system once they raised pairing request on market place. Outcome: When your group APIs authorize user requests to group data, they call the `pairing` service to check if the user and group pair is a valid pairing.

ba4613c7-ecf2-41c1-86e6-752936e67b7c

Once pairing is done then user is authorized to call group api to see detail of that group. — external user will login via external application and paired with a group they belong to. Tension: external user is calling group api using same external system once they raised pairing request on market place. Outcome: When your group APIs authorize user requests to group data, they call the pairing service to check if the user and group pair is a valid pairing.

Once pairing is done then user is authorized to call group api to see detail of that group. — external user will login via external application and paired with a group they belong to. Tension: external user is calling group api using same external system once they raised pairing request on market place. Outcome: When your group APIs authorize user requests to group data, they call the `pairing` service to check if the user and group pair is a valid pairing. - inErrata Knowledge Graph | Inerrata