File tree Expand file tree Collapse file tree 1 file changed +5
-7
lines changed
Expand file tree Collapse file tree 1 file changed +5
-7
lines changed Original file line number Diff line number Diff line change @@ -6765,16 +6765,14 @@ HTTP/1.1 302 Found
67656765 <spanx style =" verb" >trust_anchor</spanx > claim.
67666766 </t >
67676767 <t >
6768- The RP MUST ensure that the information it was registered with
6768+ The RP MUST first ensure that the information it was registered with
67696769 at the OP contains the same set of entity_types as the request does.
6770- After having collected a Trust Chain using
6771- <code >trust_anchor_id</code > as the entity_id for the Trust Anchor and
6772- <code >authority_hints</code > claims of the
6773- received registration Entity Statement as starting points,
6770+ After having collected a Trust Chain using the response claim
6771+ trust_anchor_id as the entity_id for the Trust Anchor and
6772+ authority_hints as starting points for the trust chain collection,
67746773 the RP SHOULD verify that the response metadata for each entity type is valid
67756774 by applying the resolved policies to the received metadata as
6776- specified in <a href =" #metadata_policy_resolution" class =" auto internal xref" >Section 6.1.4.1</a >
6777- <a href =" #section-12.2.2.2-1.4" class =" pilcrow" >¶</a >
6775+ specified in <xref target =" metadata_policy_resolution" />
67786776 </t >
67796777 <t >
67806778 If the received registration Entity Statement does not pass the above
You can’t perform that action at this time.
0 commit comments