/
The Architecture and Protocol Flows of Trust Router

The Architecture and Protocol Flows of Trust Router

There are typically two distinct sets of keys needed in a Trust Router-based ecosystem that Trust Router is used to negotiate - a shared key between the RP and IdP that allows those two Moonshot entities to communicate, and the shared key between the IdP and APC that is used to facilitate the generation of the first key (as it allows the IdP and APC to mutual authenticate). Thus, there are three possible scenarios for Trust Router (in order of increasing complexity) - one where both keys are already established, one where only the latter key is already established, and one where neither keys are yet established. Follow the links below to see the full protocol flow for each of these three cases.

Both keys already exist

One key already exists

No keys exist

Related content

Trust Router Protocol Flows with Existing APC/IdP Key
Trust Router Protocol Flows with Existing APC/IdP Key
More like this
Trust Router Protocol Flows with Existing RP/IdP Key
Trust Router Protocol Flows with Existing RP/IdP Key
More like this
The Trust Router configuration format (v1.0)
The Trust Router configuration format (v1.0)
More like this
Moonshot and the Trust Router
Moonshot and the Trust Router
More like this
Components of the Trust Router
Components of the Trust Router
More like this
Introduction to Trust Router
Introduction to Trust Router
More like this