hiro117 / scim

Automatically exported from code.google.com/p/scim
0 stars 0 forks source link

Remove the uniqueness requirement from externalId #79

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
In the 202 session at IIW14 we discussed removing the uniqueness requirement on 
externalid.

Original issue reported on code.google.com by e...@wahlstromstekniska.se on 16 May 2012 at 12:07

GoogleCodeExporter commented 9 years ago

Original comment by e...@wahlstromstekniska.se on 16 May 2012 at 3:41

GoogleCodeExporter commented 9 years ago

Original comment by kpgriz...@gmail.com on 18 May 2012 at 5:03

GoogleCodeExporter commented 9 years ago
Following is the suggested change in the text to fix this issue: This is also 
discussed in the mail thread on cloud-directory list: 
https://groups.google.com/group/cloud-directory/browse_thread/thread/f294730a041
59b12

Old:
Unique identifier for the Resource as defined by the Service Consumer. The 
externalId may simplify identification of the Resource between Service Consumer 
and Service provider by allowing the Consumer to refer to the Resource with its 
own identifier, obviating the need to store a local mapping between the local 
identifier of the Resource and the identifier used by the Service Provider. 
Each Resource MAY include a non-empty externalId value. The value of the 
externalId attribute is always issued be the Service Consumer and can never be 
specified by the Service Provider. This identifier MUST be unique across the 
Service Consumer's entire set of Resources. It MUST be a stable, 
non-reassignable identifier that does not change when the same Resource is 
returned in subsequent requests. The Service Provider MUST always interpret the 
externalId as scoped to the Service Consumer's tenant.

New:
An identifier for the Resource as defined by the Service Consumer. The 
externalId may simplify identification of the Resource between Service Consumer 
and Service provider by allowing the Consumer to refer to the Resource with its 
own identifier, obviating the need to store a local mapping between the local 
identifier of the Resource and the identifier used by the Service Provider. 
Each Resource MAY include a non-empty externalId value. The value of the 
externalId attribute is always issued be the Service Consumer and can never be 
specified by the Service Provider. The Service Provider MUST always interpret 
the externalId as scoped to the Service Consumer's tenant.

Original comment by hasini@wso2.com on 10 Jun 2012 at 2:07

GoogleCodeExporter commented 9 years ago
Fixed as per revision 190.

Original comment by hasini@wso2.com on 25 Jun 2012 at 3:55