...
(1), (2) and (3) are good
(4) I would like the possibility to add some additional text here. Assume 150 characters
(5) For InAcademia this should be the name for teh the (OIDC) RP, which we should register have registered in the client registry. Currently the client registry has no capability to register a display name. as a fall back this screen should always use client_id if display _ name is not available.
Also I would suggest working wording to be:
"XYZ is about to receive the following information:"
(6) The only thing we need to display here is the affiliation.
Header of the attribute should be "InAcademia will confirm your affiliation"
and then show the value(s) received from the institution.
(7) This link should show the text:
"Click here to see what information is stored by InAcademia InAcadamia as part of this transaction"
And upon selecting the link present the following information:
* the OIDC session identifier for the Service which requested the validation
* an identifier for the Service (name or entityid?)
* the session identifier as provided by the Institution (saml nameid)
* the affiliation provided by the Institution
* the IP address used at the time of the transaction
* the date and time of this transaction
(8) this question does not make sense as we do not store consent in InAcademia.
this This should be replace with a text and link to the privacy policy. selecting the link should open in a new screen, so we do not break the flow
text proposal:
"Learn about the InAcademia Data send and stored by InAcademia is subject to our Privacy Policy: https://inacademia.org/about/privacy"
(9) Both good.