Date: Tue, 19 Mar 2024 07:41:50 +0000 (UTC) Message-ID: <1775573081.1188.1710834110006@fra-prod-wiki01.geant.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1187_1994903485.1710834110003" ------=_Part_1187_1994903485.1710834110003 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The most promin= ent protocol that should be supported along with SAML in the R&E sector= is OpenID Connect (OIDC). OpenID Connect is becoming a widely accepted sta= ndard in both the commercial and the R&E sectors.
Relying Parties, or Clients, registration to the OP (OIDC Provider) is a= fundamental part of the OIDC workflow, and most of all Dynamic Client Regi= stration (1). Dynamic Client Registration is a powerful and effective way t= o enable new relying parties, but it has no attached processes to define th= e trust between the client and the OP.
OpenID Connect Federation 1.0 Draft 3 (2).
(1) https://openid.net/specs/ope= nid-connect-registration-1_0.html
(2) http://openid.net/specs/openid-= connect-federation-1_0.html
To be published
Date | Location | Agenda | Minutes |
---|---|---|---|
14:= 30 CEST |
https://webconf.vc.dfn.de/aarc-jra= 1 | First AARC2 JRA1.3 meeting | 2017-07-21 AARC2-JRA1.3B Meeting notes |