This section contains the following topics:
SSL Stops Working After an Upgrade (162487)
SharePoint Agent Cannot Access DLP-protected Document (169890)
People Picker Displays Duplicate Values for Resolved User in Google Chrome (169879)
People Picker Window is Blank in FireFox Browser (169882)
Specifying Custom Object Classes in LDAP not Supported (CQ139697)
SharePoint Credential Collector Dialog Appears (CQ140429)
SharePoint FedAuth Cookies and Office Client Integration Behavior
Duplicate Ports not Detected by Configuration Wizard
Close Browser After Logging Off with X.509 Authentication Scheme (CQ 134124)
Inconsistency between runtime Access Policy and People Picker Behavior (CQ 134290)
Cannot Access Protected SharePoint Resource using the Anonymous Authentication Scheme (CQ 135276)
Traditional Web Agents As Cookie Providers not Supported (CQ137292)
Incorrect SAML 2.0 Auto-post Message Appears During Log On (CQ 137350)
HTTP 500 Error is Displayed when SharePoint Issues a 302 as FedAuth Cookie Expires (CQ 138199)
Search for Claims works with IdentifierClaim at certain places in SharePoint
ProxyTrust agent configuration parameter not necessary (CQ 138235)
Default Location of FCC forms in Administrative UI does not Work
SharePoint Component in Profiler is for SharePoint 2007 Agent (CQ 139389)
Incorrect Trace.conf Path in LoggerConfig.properties File (CQ 142005)
SharePoint People Picker Stops Responding (CQ139284)
Backup your Existing Proxy Rules before Running Configuration Wizard (CQ142050, CQ140787)
No Assertion Consumer URL found for RP Message in Log Files (CQ141783)
Symptom:
I upgraded my CA SiteMinder® Agent for SharePoint, but my SSL connections stopped working.
Solution:
Generate a new SSLConfig properties file by performing the following steps:
Run the GenerateSSLConfig script installed with the Agent for SharePoint to generate an SSLConfig.properties file for the keystore. SSLConfig.properties is required to protect the Claims WS service.
GenerateSSLConfig uses the following syntax:
GenerateSSLConfig -keystorepass password_to_your_keystore
Follow these steps:
Agent-for-SharePoint_home\proxy-engine\bin
You specify the following parameters when you run the script:
Specifies the password for the keystore.
If an SSLConfig.properties file exists, an overwrite warning appears.
A confirmation message confirms the keystore was configured and displays the directory of the keystore you created. The SSLConfig.properties file is generated.
Symptom:
Unable to access the DLP-protected document because the DLP application cannot retrieve the content identifier from the SharePoint Agent.
Solution:
When you use the SharePoint Agent with the DLP integration, follow these steps:
org.apache.tomcat.util.http.ServerCookie. ALLOW_HTTP_SEPARATORS_IN_V0=true
Symptom:
When you add a user to the site permissions, the user details are populated twice in the grant permission window. This occurs when using Google Chrome to view the site.
Solution:
There is no work around for this issue.
Symptom:
In the People Picker grant permission window, click the user/group button. The Select People and Groups window is blank when it displays in a Firefox browser. The window does not display any objects against which to search.
Solution:
Resize the People Picker window and it displays the objects.
Symptom:
If you try to install SharePoint 2010 or later on a machine with CA SiteMinder® Agent for SharePoint or the CA SiteMinder® Agent for SharePoint, the installer detects that SharePoint already exists.
Solution:
The installation of SharePoint on a machine with CA SiteMinder® Agent for SharePoint or the CA SiteMinder® Agent for SharePoint is not supported.
Symptom:
I use custom object classes in my LDAP directory, and I set the registry setting correctly in the Policy Server.
Can I list the names of my custom object classes instead of using an asterisk, as the CA SiteMinder® Agent for SharePoint documentation indicates?
Solution:
No. This version requires an asterisk if custom object classes are used.
Symptom:
Some users see a SharePoint credential collector dialog when they try to access a protected resource.
Solution:
This dialog appears when users access a SharePoint web application that has more than one claims provider type configured on a zone. The dialog contains a drop-down list of each provider. Multiple providers exist for different reasons.
If this dialog appears, select the SiteMinder provider to proceed.
Copyright © 2014 CA.
All rights reserved.
|
|