From 4b4242b3d4cac29866c003f59eb43af48c9b4dfb Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Fri, 8 Oct 2021 12:38:17 -0500 Subject: [PATCH] Update future-proofed-and-federation-ready-enterprise-ids.adoc --- future-proofed-and-federation-ready-enterprise-ids.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/future-proofed-and-federation-ready-enterprise-ids.adoc b/future-proofed-and-federation-ready-enterprise-ids.adoc index 4b6f031..e18b2fd 100644 --- a/future-proofed-and-federation-ready-enterprise-ids.adoc +++ b/future-proofed-and-federation-ready-enterprise-ids.adoc @@ -29,7 +29,7 @@ Relying parties should not treat this identifier as an email address for the sub *The unique ID should not change as a result of a change to any other data associated with the subject (e.g., name, email address, age, organizational role)* This essentially forbids the use of name-based identifiers since it is impossible to guarantee that name-based identifiers will never change. -A given value MUST identify the same subject regardless of the context of use or the relying parties to which the Attribute is given. It is therefore to be assumed by relying parties that receive a given value that the same subject has been identified. +A given value MUST identify the same subject regardless of the context of use or the relying parties to which the attribute is given. It is therefore to be assumed by relying parties that receive a given value that the same subject has been identified. A single subject MAY be identified simultaneously by a single asserting party by multiple values, but this should be minimized to the extent possible.