Skip to content

Commit 143061e

Browse files
committed
Clarified Explicit Client Registration Lifetime
1 parent a843e70 commit 143061e

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

openid-federation-1_0.xml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7458,15 +7458,14 @@ HTTP/1.1 302 Found
74587458
</t>
74597459
</section>
74607460

7461-
<section title="After an Explicit Client Registration" anchor="AfterExplicitReg">
7461+
<section title="Explicit Client Registration Lifetime" anchor="AfterExplicitReg">
74627462
<t>
74637463
An RP can utilize the <spanx style="verb">exp</spanx> Claim of the
74647464
registration Entity Statement to devise a suitable strategy for
74657465
renewing its client registration. RP implementers should note that
7466-
if the OP expiration of the <spanx style="verb">client_id</spanx>
7467-
coincides with an OAuth 2.0 flow that was just initiated by the RP, this
7468-
may cause OpenID Connect authentication requests, token requests, or
7469-
UserInfo requests to suddenly fail. Renewing the RP registration
7466+
if the the RP's registration has expired at the OP,
7467+
this can cause OpenID Connect authentication requests, token requests,
7468+
and/or UserInfo requests to fail. Renewing the RP's registration
74707469
prior to its expiration can prevent such errors from
74717470
occurring and ensure the end-user experience is not disrupted.
74727471
</t>

0 commit comments

Comments
 (0)