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
WaTTS enables an rsp endpoint at
/rsp at wich an RSP can redirect its users. The full path to redirect to is
<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.
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:
WaTTS expects the following keys to be present:
kty of "RSA"
use of "sig"
alg of "RS256"
kid which must also be set in the JWT sent by the RSP
n (part of the public key)
e (part of the public key)
The RSP must implement or use a JWT library to sign the JWTs with the private part of the keys mentioned above.
The Jwt header MUST contain the key value pair
The following claims in the JWT are supported:
The Id of the RSP in the configuration file at WaTTS
The representation of the user at the RSP
The expiration time of the jwt see RFC7519
The time at which the jwt was issued see RFC7519
The Id of the service to trigger at WaTTS
The parameter to pass to the service at WaTTS
The Id of the OpenID Connect provider to use for logging in
The url to redirect to in case of success, if not set WaTTs will redirect to the referer
The url to redirect to in case of failure, if not set WaTTs will redirect to success_url