70-158 · Question #58
You deploy Forefront Identity Manager (FIM) 2010 in your company network. You need to activate Kerberos authentication for the FIM Portal. What should you do?
The correct answer is A. Modify the ResourceManagementClient section of the web.config file. To activate Kerberos authentication for the Forefront Identity Manager (FIM) 2010 Portal, you must modify the FIM Portal's configuration file to specify Kerberos for its service communication. This involves editing a specific section within the web.config file.
Question
Options
- AModify the ResourceManagementClient section of the web.config file.
- BFrom the Internet Information Services (IIS) Manager console,
- CFrom the SharePoint Central Administration website, on the Edit Authentication page,
- DFrom the SharePoint Central Administration website, on the Edit Authentication page,
How the community answered
(20 responses)- A75% (15)
- B5% (1)
- C15% (3)
- D5% (1)
Why each option
To activate Kerberos authentication for the Forefront Identity Manager (FIM) 2010 Portal, you must modify the FIM Portal's configuration file to specify Kerberos for its service communication. This involves editing a specific section within the web.config file.
To enable Kerberos authentication for the FIM Portal's communication with the FIM Service, the `ResourceManagementClient` section within the FIM Portal's `web.config` file needs to be updated. This section defines the client bindings for the underlying Windows Communication Foundation (WCF) service calls, where the authentication type can be explicitly set to Kerberos. This ensures the client-side communication uses Kerberos for secure authentication with the FIM Service.
Configuring settings in IIS Manager is too general and typically relates to the web server's authentication rather than the specific FIM Portal's internal communication client settings. It doesn't target the FIM service client binding directly.
Configuring authentication from SharePoint Central Administration applies to the SharePoint web application itself, not specifically to the FIM Portal's internal communication with the FIM Service client, which uses distinct WCF bindings.
This option is identical to option C and is incorrect for the same reason, as it addresses general SharePoint web application authentication rather than FIM's specific client configuration.
Concept tested: FIM Portal Kerberos authentication configuration
Topics
Community Discussion
No community discussion yet for this question.