Currently, the SPSP endpoint that the query is proxied to is cached with the receipt nonce and returned in the /verify response.
In cases when the SPSP_ENDPOINTS_URL might return the same SPSP endpoint for multiple id's, it would be useful to know the original id / SPSP query path.
When SPSP_ENDPOINTS_URL is configured, the /verify response can include an id field:
This would be useful in Codius where the paths of the original SPSP query urls correspond to particular functions, but the SPSP_ENDPOINTS_URL regularly returns the single SPSP endpoint of the Codius host.
Currently, the SPSP endpoint that the query is proxied to is cached with the receipt nonce and returned in the
/verify
response.In cases when the
SPSP_ENDPOINTS_URL
might return the same SPSP endpoint for multiple id's, it would be useful to know the original id / SPSP query path.When
SPSP_ENDPOINTS_URL
is configured, the/verify
response can include anid
field:This would be useful in Codius where the paths of the original SPSP query urls correspond to particular functions, but the
SPSP_ENDPOINTS_URL
regularly returns the single SPSP endpoint of the Codius host.