Skip to content

Commit 0e05ca7

Browse files
authored
Merge pull request #322 from openid/mbj-group-text
Reorder to group protocol-independent text together
2 parents 7d8e74c + 300de17 commit 0e05ca7

File tree

1 file changed

+36
-27
lines changed

1 file changed

+36
-27
lines changed

openid-federation-1_0.xml

Lines changed: 36 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -509,6 +509,9 @@
509509
<spanx style="verb">kid</spanx> (Key ID) header parameter
510510
with its value being the Key ID of the signing key used.
511511
</t>
512+
513+
<section anchor="ESClaims" title="Entity Statement Claims">
514+
512515
<t>
513516
The Claims in an Entity Statement are listed below.
514517
Applications and protocols utilizing Entity Statements MAY specify
@@ -808,6 +811,8 @@
808811
</list>
809812
</section>
810813

814+
</section>
815+
811816
<section anchor="ESValidation" title="Entity Statement Validation">
812817
<t>
813818
Entity Statements MUST be validated in the following manner.
@@ -982,6 +987,24 @@
982987
to validate that this is the fetch endpoint
983988
from which the Entity Statement was issued.
984989
</t>
990+
<t>
991+
If the <spanx style="verb">trust_chain</spanx> header parameter is present,
992+
validate that its value is a syntactically valid Trust Chain,
993+
as specified in <xref target="trust_chain"/>.
994+
The first entry in the Trust Chain
995+
MUST be an Entity Configuration for this Entity.
996+
Implementations SHOULD validate that the Entity Identifier
997+
for the Trust Anchor at the end of the Trust Chain matches
998+
one of the Trust Anchors configured for the deployment.
999+
</t>
1000+
<t>
1001+
If the <spanx style="verb">peer_trust_chain</spanx> header parameter is present,
1002+
validate that its value is a syntactically valid Trust Chain,
1003+
as specified in <xref target="trust_chain"/>.
1004+
Implementations SHOULD validate that the Entity Identifier
1005+
for the Trust Anchor at the end of the Trust Chain matches
1006+
one of the Trust Anchors configured for the deployment.
1007+
</t>
9851008
<t>
9861009
If the <spanx style="verb">aud</spanx> Claim is present,
9871010
if the Entity Statement is an Explicit Registration request,
@@ -1006,24 +1029,6 @@
10061029
Explicit Registration responses
10071030
unless its use is otherwise specified in an extension being employed.
10081031
</t>
1009-
<t>
1010-
If the <spanx style="verb">trust_chain</spanx> header parameter is present,
1011-
validate that its value is a syntactically valid Trust Chain,
1012-
as specified in <xref target="trust_chain"/>.
1013-
The first entry in the Trust Chain
1014-
MUST be an Entity Configuration for this Entity.
1015-
Implementations SHOULD validate that the Entity Identifier
1016-
for the Trust Anchor at the end of the Trust Chain matches
1017-
one of the Trust Anchors configured for the deployment.
1018-
</t>
1019-
<t>
1020-
If the <spanx style="verb">peer_trust_chain</spanx> header parameter is present,
1021-
validate that its value is a syntactically valid Trust Chain,
1022-
as specified in <xref target="trust_chain"/>.
1023-
Implementations SHOULD validate that the Entity Identifier
1024-
for the Trust Anchor at the end of the Trust Chain matches
1025-
one of the Trust Anchors configured for the deployment.
1026-
</t>
10271032
</list>
10281033
</t>
10291034
<t>
@@ -7840,23 +7845,23 @@ HTTP/1.1 302 Found
78407845
</t>
78417846
</section>
78427847

7843-
<section anchor="explicit-registration-response+jwt"
7844-
title='"application/explicit-registration-response+jwt" Media Type'>
7848+
<section anchor="trust-mark-status-response+jwt"
7849+
title='"application/trust-mark-status-response+jwt" Media Type'>
78457850
<t>
7846-
The <spanx style="verb">application/explicit-registration-response+jwt</spanx>
7851+
The <spanx style="verb">application/trust-mark-status-response+jwt</spanx>
78477852
media type is used to specify that the associated content is
7848-
an Explicit Registration response, as defined in <xref target="cliregresp"/>.
7853+
a Trust Mark Status Response,
7854+
as defined in <xref target="tm-status-response"/>.
78497855
No parameters are used with this media type.
78507856
</t>
78517857
</section>
78527858

7853-
<section anchor="trust-mark-status-response+jwt"
7854-
title='"application/trust-mark-status-response+jwt" Media Type'>
7859+
<section anchor="explicit-registration-response+jwt"
7860+
title='"application/explicit-registration-response+jwt" Media Type'>
78557861
<t>
7856-
The <spanx style="verb">application/trust-mark-status-response+jwt</spanx>
7862+
The <spanx style="verb">application/explicit-registration-response+jwt</spanx>
78577863
media type is used to specify that the associated content is
7858-
a Trust Mark Status Response,
7859-
as defined in <xref target="tm-status-response"/>.
7864+
an Explicit Registration response, as defined in <xref target="cliregresp"/>.
78607865
No parameters are used with this media type.
78617866
</t>
78627867
</section>
@@ -11510,6 +11515,10 @@ Host: op.umu.se
1151011515
</t>
1151111516
<t>
1151211517
Made section and figure titles more consistent.
11518+
</t>
11519+
<t>
11520+
Reordered some text to group protocol-independent text together
11521+
and protocol-specific text together.
1151311522
</t>
1151411523
<t>
1151511524
Applied suggestions from Nat Sakimura improving the descriptions of

0 commit comments

Comments
 (0)