可信赖的提供商的Sharepoint 2010标识符声明 [英] Sharepoint 2010 Identifier Claim for Trusted Provider
问题描述
您好,
在为Sharepoint创建(New-SPTrustedIdentityTokenIssuer)时,建议选择 标识符声明? (非ADFS)是否重要?
what is recommended for choosing identifier Claim when creating (New-SPTrustedIdentityTokenIssuer) for Sharepoint? (Non-ADFS) Does it matter?
无法使用任何 Sharepoint-reserved索赔类型如
Its not possible to use any of Sharepoint-reserved Claim Types like
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier
或 http://schemas.microsoft.com / sharepoint / 2009/08 / claim / userid zh
创建可信赖的提供商时
收到的索赔是 一个用户唯一ID,但我可以使用电子邮件或者UPN声明类型作为localclaimtype:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
或
http:// schemas。 xmlsoap.org/ws/2005/05/identity/claims/upn
$
这将导致编码的名称如 0e.t |供应商|用户id 或
05.t |供应商|用户ID
有规格列出索赔类型为
http://schemas.microsoft.com/sharepoint/2009/08/claims/useridentifier
这里:
http ://download.microsoft.com/download/8/5/8/858F2155-D48D-4C68-9205-29460FD7698F/ [MS-SPSTWS] .pdf
实际上导致编码名称如0ǵ.t| provider | userid(编码字符不是"如规范中所述)
b
这是规范中的拼写错误并且意味着
http://download.microsoft.com/download/8/5/8/858F2155-D48D-4C68-9205-29460FD7698F/[MS-SPSTWS].pdf
what in fact leads to encoded Names like 0ǵ.t|provider|userid (the encoded character is not " as stated in the specification)
Is it a typo in the spec and meant to be
SPClaimTypes.UserIdentifier //http://schemas.microsoft.com/sharepoint/2009/08/claims/userid
推荐答案
使用电子邮件地址作为identifierclaim有什么不舒服?我听过人们使用其他任何东西的恐怖故事。
What is your discomfort with using email address as the identifierclaim? I have heard horror stories of people using anything else.
这篇关于可信赖的提供商的Sharepoint 2010标识符声明的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!