-
Notifications
You must be signed in to change notification settings - Fork 1k
Customer Security PreTrimmer needs Updating for SharePoint 2019 #7995
Copy link
Copy link
Closed
Labels
area:docsCategory: SharePoint developer/development documentation relatedCategory: SharePoint developer/development documentation relatedarea:docs-commentCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devtype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active work
Metadata
Metadata
Assignees
Labels
area:docsCategory: SharePoint developer/development documentation relatedCategory: SharePoint developer/development documentation relatedarea:docs-commentCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devCategory: Comment left on bottom of a docs page here: https://docs.microsoft.com/sharepoint/devtype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active work
Type
Fields
Give feedbackNo fields configured for issues without a type.
Guidance needs to be updated for SharePoint 2019. Microsoft.Office.Server.Search.Query is now compiled using .NET Framework 4.8 which utilizes WIF from System.Security.Claims instead of Microsoft.IdentityModel.Claims. Minimal changes are required for PreTrimmer:
Useful References:
https://docs.microsoft.com/en-us/previous-versions/dotnet/framework/windows-identity-foundation/guidelines-for-migrating-an-application-built-using-wif-3-5-to-wif-4-5
https://docs.microsoft.com/en-us/previous-versions/dotnet/framework/windows-identity-foundation/namespace-mapping-between-wif-3-5-and-wif-4-5
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.