An RSP is a service that relys on WaTTS to either perform tasks or to authenticate users for it, or both.
Any RSP that wants to rely on WaTTS needs to be configured as described in the configuration guide. The two important steps are:
enable RSP support with enable_rsp = true
configure the RSP according to the 'Relying Service Provider' configuration
How it works
WaTTS enables an rsp endpoint at /rsp at wich an RSP can redirect its users. The full path to redirect to is https://watts-host/rsp/<jwt>.
The <jwt> is a JSON Web Token (JWT) generated and signed by the RSP. WaTTS will verify the JWT and perform the requested actions, if allowed.
On error or success the user gets redirected back to the RSP.
What an RSP needs to implement
A JWK endpoint
WaTTS needs an endpoint to fetch the public keys used to sign the JWT. The json format of the plublic keys file must be according to RFC7517. The following is an example: