Currently the Claims Provider is packaged in a single SharePoint solution with:
The Claims Provider (scope=Farm)
The settings page for Central Admin (scope=Web)
Now because we have a Web feature in this solution this solution will only be deployed on servers which are running the Microsoft SharePoint Foundation Web Application service. On other servers (your application servers) this solution will not be deployed, which means the assembly will also not be in the Gac.
This could cause some issues with services that depend on the Claims Provider to resolve the user's identity (eg: Search).
This is why it might be better to have 2 solutions: one with the Farm features and one with the Web features.
Currently the Claims Provider is packaged in a single SharePoint solution with:
scope=Farm)scope=Web)Now because we have a Web feature in this solution this solution will only be deployed on servers which are running the
Microsoft SharePoint Foundation Web Applicationservice. On other servers (your application servers) this solution will not be deployed, which means the assembly will also not be in the Gac.This could cause some issues with services that depend on the Claims Provider to resolve the user's identity (eg: Search).
This is why it might be better to have 2 solutions: one with the Farm features and one with the Web features.