Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below is an architecture diagram of a third party push. Panintelligence will receive data from the third party system that contains user data at regular intervals.

Drawio
mVer2
zoom1
simple0
zoominComment10
inCommentcustContentId01900675092
pageId1899626497
custContentIdlbox19006750921
diagramDisplayNameUntitled Diagram-1723127272428.drawiolbox1
contentVer2
revision2
baseUrlhttps://panintelligence.atlassian.net/wiki
diagramNameUntitled Diagram-1723127272428.drawio
pCenter0
width749
links
tbstyle
height392.611083984375

Possible architectural patterns

Since the third party system either pushes the data to panintelligence via the Panintelligence API or receives data as a composite of the claims data within the JWT, there are few architectural considerations to make.

Authentication push

Your authentication server will need to have a route defined to the panintelligence API. It is advisable to do this via your load balancer.

Oauth JWT

If you’re accessing your authentication system defined as Oauth, you will need to define a route from your Panintelligence application server to your authentication server. For egress access, it is advisable to create an egress-only gateway to limit access from the internet to your application layer.

Drawio
mVer2
simple0
zoom1
inComment0
pageId1899626497
custContentId1902149675
diagramDisplayNamearch-sec.drawio
lbox1
contentVer1
revision1
baseUrlhttps://panintelligence.atlassian.net/wiki
diagramNamearch-sec.drawio
pCenter0
width901.0000000000001
links
tbstyle
height1010.5000000000001