 PDF 文書ファイルをダウンロードする (662 KB)
Sun OpenSSO Enterprise 8.0 Release NotesLast revised June 18, 2009 SunTM OpenSSO Enterprise 8.0 is part of the OpenSSO project (http://opensso.org/) and is the Sun commercial version of OpenSSO server. These Release Notes also apply to Sun OpenSSO Express. OpenSSO Enterprise and OpenSSO Express are essentially the same product, but they have these differences:
Note – If you are using WebLogic Server as the web container to deploy OpenSSO Enterprise server, see 4077: OpenSSO Enterprise configuration on WebLogic Server requires new ldapjdk.jar. Contents Getting Started With OpenSSO Enterprise 8.0If you have not previously installed OpenSSO Enterprise, here are the basic steps to follow:
OpenSSO Enterprise 8.0 DocumentationThe OpenSSO Enterprise 8.0 documentation is available on the following site: http://docs.sun.com/coll/1767.1 Check this site periodically to view the most recent documentation. OpenSSO Enterprise 8.0 Update 1OpenSSO Enterprise 8.0 Update 1 is available as patch 141655-01 on http://sunsolve.sun.com/. Update 1 includes a WAR file (opensso.war) that you can use to patch OpenSSO Enterprise 8.0 or install as a new OpenSSO Enterprise 8.0 Update 1 deployment. For information about Update 1, including new features, hardware and software requirements, installation, and known issues with workarounds, see the OpenSSO Enterprise 8.0 Update 1 Release Notes at http://wikis.sun.com/x/SAP7BQ. Patches to Update 1Sun periodically releases patches to OpenSSO Enterprise 8.0 Update 1 on http://sunsolve.sun.com/. To find the latest patch for Update 1, search for patch ID 141655. To determine if you should install a patch, check the README file available with the patch. Each patch release includes an opensso.war file that you can deploy as follows:
For more information see, “Installing OpenSSO Enterprise 8.0 Update 1” at http://wikis.sun.com/x/RgQCBg. What’s New in OpenSSO Enterprise 8.0OpenSSO Enterprise 8.0 includes features such as access management, federation management, and web services security that are found in earlier releases of Sun Java System Access Manager and Sun Java System Federation Manager. OpenSSO Enterprise also includes the new features described in this section. For the new features in version 3.0 policy agents, see one of these guides:
Using Service Tags With Sun InventoryOpenSSO 8.0 is Service Tag enabled, which allows you to use Sun Inventory to track and organize your OpenSSO product (as well as other hardware and software products). To use Service Tags, you must first register your product. You can register OpenSSO Enterprise, OpenSSO Express, or even a nightly build. To register, you need a Sun Online Account (SOA) or Sun Developer Network (SDN) account. If you do not have one of these accounts, you can get an account during the product registration process. To register your OpenSSO product and start using Service Tags, follow these steps:
Service Tag registration files are stored in the config-directory/deployuri/lib/registration directory. For example: opensso-config/opensso/lib/registration. For more information, see:
Check these sites to see if Service Tags are supported on your specific platform, or if you need to determine if a specific OpenSSO server is already registered. Hardware and Software Requirements For OpenSSO Enterprise 8.0Note – The hardware and software requirements for OpenSSO Enterprise 8.0 described in this section represent the only environments in which it can be deployed with full support from Sun Microsystems. No support is provided for environments that do not meet the stated requirements. Sun Microsystems assumes no responsibility or liability for any environments that don't adhere to supported hardware and software requirements for OpenSSO Enterprise 8.0 as documented. Sun strongly recommends that you involve the Sun Professional Services organization before you begin the installation and deployment process. This may require additional expense on your part.  Caution – If you plan to use the OpenSSO configuration data store, you must deploy OpenSSO Enterprise on a local file system and not on an NFS-mounted file system. The OpenSSO configuration data store, which is deployed with OpenSSO Enterprise, is not supported on an NFS-mounted file system. Platforms Supported For OpenSSO Enterprise 8.0Table 1 Platforms Supported For OpenSSO Enterprise 8.0
Web Containers Supported For OpenSSO Enterprise 8.0Table 2 Web Containers Supported For OpenSSO Enterprise 8.0
For more information, including considerations and pre-deployment tasks for each web container, see Chapter 2, Deploying the OpenSSO Enterprise Web Container, in Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide. JDK Requirements For OpenSSO Enterprise 8.0Table 3 JDK Requirements For OpenSSO Enterprise 8.0
Data Store Requirements For OpenSSO Enterprise 8.0Table 4 Data Store Requirements For OpenSSO Enterprise 8.0
For more information about data stores, see Chapter 2, Building the Deployment Architecture, in Sun OpenSSO Enterprise 8.0 Deployment Planning Guide. Session Failover Requirements for OpenSSO Enterprise 8.0Table 5 Session Failover Requirements for OpenSSO Enterprise 8.0
For more information, see Chapter 7, Implementing OpenSSO Enterprise Session Failover, in Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide. Policy Agents Supported for OpenSSO Enterprise 8.0Table 6 Policy Agents Supported for OpenSSO Enterprise 8.0
Database Logging Requirements For OpenSSO Enterprise 8.0Table 7 Database Logging Requirements For OpenSSO Enterprise 8.0
Hardware Requirements For OpenSSO Enterprise 8.0Table 8 Hardware Requirements For OpenSSO Enterprise 8.0
Web Browsers Supported For OpenSSO Enterprise 8.0Table 9 Web Browsers Supported For OpenSSO Enterprise 8.0
OpenSSO Enterprise 8.0 IssuesFor more information about OpenSSO Enterprise issues, see: https://opensso.dev.java.net/servlets/ProjectIssues Web Container and Server Issues
4077: OpenSSO Enterprise configuration on WebLogic Server requires new ldapjdk.jarOpenSSO Enterprise configuration fails on WebLogic Server because weblogic.jar bundles an older ldapjdk.jar file. Sun provides a new ldapjdk.jar file that includes security and performance related fixes. You must provide the following workaround for both WebLogic Server 9.2 and WebLogic Server 10. Workaround. Put the Sun ldapjdk.jar ahead of weblogic.jar in the CLASSPATH, as follows:
WebLogic Server StuckThreadMaxTime value is exceeded during configurationIf you are configuring WebLogic Server 9.2 MP2 or 10 using the Configurator and you take longer than 600 seconds to finish the configuration, the following error is returned to the terminal and WebLogic Server domain and server logs: <Error> <WebLogicServer> <BEA-000337> <[STUCK] Exe cuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "681" seconds working on the request "Http Request: /opensso/setup/setSetup Progress", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: ... This error occurs because the WebLogic Server has exceeded its “Stuck Thread Max Time:” default value of 600 seconds. Workaround. If the Configurator does not respond, restart it. Also, consider setting the WebLogic Server “Stuck Thread Max Time” value from its default 600 seconds to a larger value such as 1200 seconds. Use the WebLogic Console to change this value (base_domain > Environment > Servers > Admin Server > Configuration/Tuning). 4099: ID-WSF sample with JDK 1.4 WAR returned exceptionOn WebLogic Server 8.1, opensso-client-jdk14.war configured for ID-WSF returned an error when looking for service. Workaround. Add following JAR files under weblogic-home/jdk142_08/jre/lib/endorsed:
These JAR files are available in the following ZIP file: http://download.java.net/general/opensso/stable/issues/issue_4099.zip 4094: Multi-server setup fails when amadmin password and directory manager password for configuration data store are not the sameThis issue occurs only if the following conditions are met:
Workaround. There are two parts to this workaround:
4055: Error occurred after adding an advanced property in consoleAdding an advanced property in the Console caused OpenSSO Enterprise server to return an error. This problem can occur after adding any advanced configuration property. Workaround. If you change the default server configuration in the Console, you must restart the OpenSSO Enterprise server web container. 3858: Out of memory exceptions occur under heavy load with JDK 1.5 and 1.6 SunPKCS11 providerJDK 1.5 and 1.6 contain a list of PKCS11 providers. The default is sun.security.pkcs11.SunPKCS11 (see the provider list below). Under a heavy load, this provider will generate an Out of Memory Exception (OOME) for the web container and cause the container to crash. At minimum, the following scenarios are impacted:
The issue is currently under investigation and might impact other web container platforms not listed above. Workaround. Remove the SunPKCS11 provider from the provider list in the java.security file for the JVM. For example, if the security provider section in your java.security file (found in JDK_Path/jre/lib/security/) looks like: security.provider.1=sun.security.pkcs11.SunPKCS11 \
${java.home}/lib/security/sunpkcs11-solaris.cfg
security.provider.2=sun.security.provider.Sun
security.provider.3=sun.security.rsa.SunRsaSign
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.crypto.provider.SunJCE
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.sun.security.sasl.Provider
Change it to: security.provider.1=sun.security.provider.Sun security.provider.2=sun.security.rsa.SunRsaSign security.provider.3=com.sun.net.ssl.internal.ssl.Provider security.provider.4=com.sun.crypto.provider.SunJCE security.provider.5=sun.security.jgss.SunProvider security.provider.6=com.sun.security.sasl.Provider Note. This workaround can lower your performance because the provider used now is not as optimized as the SunPKCS11 provider. It also prevents you from using hardware security tokens if the SunPKCS11 provider is required. 3837: Configuration fails on Oracle Application Server 10gWith Oracle Application Server 10g version 10.1.3.1 as the web container, OpenSSO Express configuration failed with an exception error. Workaround. Before you configure OpenSSO, add the following JVM option to the “Server Properties” for the target Oracle Application Server 10g server instance: -Doc4j.jmx.security.proxy.off=true 2222: Password reset and account lockout services report notification errorsOpenSSO Enterprise submits email notifications using the unqualified sender name, Identity-Server, which returns error entries in the logs. Workaround. Change the sender name from Identity-Server to Identity-Server@hostname.domainname in the following files:
Data Store Issues
4102: TTL for service management configuration is not workingTime to live (TTL) for service management configuration is not working because the TTL property is not being initialized. 4085: OpenSSO Enterprise is unable to store the CRL in the LDAP directoryAfter getting the certificate revocation list (CRL) from the CRL distribution point extension, OpenSSO Enterprise does not store the CRL in the LDAP directory. 3827: Replication configuration hangs on second Glassfish instanceIn this scenario, OpenSSO Enterprise is deployed on two Glassfish (or Application Server 9.1) instances on Windows Vista server. During the configuration of the second OpenSSO Enterprise instance, replication of the configuration using the “Add to Existing Deployment” option hangs. Workaround. This issue still exists on Windows Vista systems. For Windows systems other than Vista, add the following Glassfish (or Application Server 9.1) JVM option: -Dcom.sun.enterprise.server.ss.ASQuickStartup=false 3350, 2867: LDAP Follows Referral should be disabled for Active Directory Data StoreAn Active Directory data store sometimes hangs the system. This problem can also occur when you are creating a new Active Directory data store. Workaround. In the OpenSSO Enterprise Admin Console, disable LDAP Follows Referral for the Active Directory data store:
Failover does not occur for Access Manager SDK (AMSDK) plug-inIf OpenSSO Enterprise is configured with the AMSDK plug-in and the directory server is set up for MMR, failover does not occur if a directory server instance goes down. Authentication Issues4103: Windows Desktop SSO authentication module returns “No Configuration Found” errorIf you configure a Windows Desktop SSO authentication module to perform a Kerberos authentication from Internet Explorer 6.0 on Windows Server 2003, the “No configuration found" error is returned. 4100: Certificate authentication with CRL checking failsIf you configure Certificate authentication and enable “Match Certificate to CRL” the authentication fails. See also the related issue 4085: OpenSSO Enterprise is unable to store the CRL in the LDAP directory. 4054: amadmin authentication fails with URL org parameterIf the OpenSSO Enterprise Admin (amadmin) creates a new realm (such as myorg) and later tries to log in to the new realm as follows: http://host:port/opensso/UI/Login?org=myorg OpenSSO Enteprise returns an Authentication Failed error. Workaround. As amadmin, you can log in only to the root realm (and only to Data Store or Application modules). 1781: amadmin login fails for non Data Store authenticationIf you change the authentication module for the root realm to anything besides DataStore, amadmin will not be able to log into the Console. Workaround. Log in using http://host.domain/deployurl/UI/Login?module=DataStore. Policy Issues
3952: Server samples are missing the policy samples linkThe index.html under host:port/uri/samples displays: 1. Authentication Samples 2. ID-FF Sample 3. SAMLv2 Sample 4. Multi-Federation Protocols Sample However, the following link to the policy samples is missing in index.html: host:port/uri/samples/policy/policy-plugins.html Workaround: Open the host:port/uri/samples/policy/policy-plugins.html file in your browser. 3949: OCSP checking needs permission added to server.policy fileTo enable OCSP checking for an OpenSSO web container that has enabled the Java Security Manager, add the following permission to the server.policy (or equivalent) file: permission java.security.SecurityPermission "getProperty.ocsp.*"; 3796: Creation of Fedlet in console failed in a console only deploymentIf you generate a console only deployment, creating a Fedlet using the Console Common Tasks failed with an error message stating that there was no file or directory for sp-extended.xml. The com.iplanet.services.configpath property was not set by the console only Configurator. Workaround. Edit the AMConfig.properties file and set the com.iplanet.services.configpath property to the configuration directory. For example: com.iplanet.services.configpath=/consoleonly 2381: Access Manager Roles policy subject is supported only with Access Manager repository data storeThe Access Manager Roles policy subject is supported only with the Access Manager Repository (AMSDK) data store. By default, this subject is disabled in the policy configuration. Therefore, enable the Access Manager Roles policy subject only if the data store type is configured to use the AMSDK plug-in. For more information, see Chapter 14, Enabling the Access Manager SDK (AMSDK) Identity Repository Plug-in, in Sun OpenSSO Enterprise 8.0 Installation and Configuration Guide. Session Issues
3910: setup.bat of ssoSessionTools.zip fails to install toolsAfter you unzip ssoSessionTools.zip, running the setup.bat script fails to install the session scripts and returns the following error: Unable to locate JRE meeting specification "1.4+" Workaround. In the setup.bat script, remove -version:"1.4+" from the java.exe command and rerun the script. 2827: Configuring a site does not add the second server to the siteSession failover configuration does not add the second OpenSSO Enterprise instance to the assigned servers list. Workaround. Use the OpenSSO Enterprise Console or ssoadm utility to manually add the second server instance to the servers list. Command-Line Utilities Issues4079: ssoadm import-svc-cfg command fails when using Directory Server as the configuration data storeSometimes the import-svc-cfg subcommand fails because OpenSSO Enterprise cannot delete nodes in the Service Manager data store. The following scenarios can cause this problem:
Workaround. Re-execute the ssoadm import-svc-cfg command until it succeeds. 3955: Unable to execute the ssoadm commandYou are unable to execute the ssoadm command with the get-realm due to this exception. Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed
com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction:
FATAL ERROR: Cannot obtain Application SSO token.
Check AMConfig.properties for the following properties
com.sun.identity.agents.app.username
com.iplanet.am.service.password
Logging configuration class "com.sun.identity.log.s1is.LogConfigReader" failed
com.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction:
FATAL ERROR: Cannot obtain Application SSO token.
Check AMConfig.properties for the following properties
com.sun.identity.agents.app.username
com.iplanet.am.service.password
AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
Check AMConfig.properties for the following properties
com.sun.identity.agents.app.username
com.iplanet.am.service.password
Check if the amadmin password is different from the directory manager password for the service management data store. If yes, apply the following workaround. Workaround. Modify the server configuration XML as follows:
2905: jss4.jar entry is missing in the ssoadm classpathAfter running the setup script for the ssoadm utility, trying to run ssoadm returns a NoClassDefFoundError error. This problem occurs for an upgraded OpenSSO Enterprise instance. Workaround. To use JSS, add jss4.jar to the classpath and set the LD_LIBRARY_PATH environment variable. (If you are using the default JCE, jss4.jar is not required to be in the classpath.) Client SDK Issues4081: SMS cache is disabled by default on the Client SDKFor a Client SDK installation, the service management service (SMS) cache is disabled by default. Workaround: For Web Services Security (WSS) applications, set com.sun.identity.sm.cache.enabled=false in the AMConfig.properties file; otherwise the fix for issue 3171 will not work. For all other Client SDK applications, set com.sun.identity.sm.cache.enabled=true in the AMConfig.properties file to enable SMS caching, which can prevent performance problems. 4080: Client SDK Configurator puts the wrong shared secret in the AMConfig.properties fileThe Client SDK WAR file Configurator puts the wrong shared secret in the AMConfig.properties file. Workaround. Copy the shared secret value and the password encryption key from the OpenSSO Enterprise server to the Client SDKAMConfig.properties file under the $HOME/OpenSSOCLient directory. Federation and SAML Issues
3923: Creating an entity (IDP or SP) in Console Common Tasks page fails on Oracle Application ServerWith OpenSSO Enterprise deployed on Oracle Application Server, creating an entity (IDP or SP) in the Console Common Tasks page causes an exception. Workaround. When opensso.war is deployed on Oracle Application Server, disable the import option for the oracle.xml file in the deployment plan view (Deploy: Deployment Settings > Configure Class Loading > oracle.xml). 3065: Same context ID is used for all users in ID-FF log recordsAll ID-FF log records have same the context (or login) ID, even if they are for different users. 2661: logout.jsp did not compile on WebSphere Application Server 6.1The logout.jsp file requires JDK 1.5, but the JDK source level for JSP files is set to JDK 1.3 on IBM WebSphere Application Server 6.1. Workaround. See the workaround for 1977: SAMLv2 sample configure.jsp files fail on WebSphere Application Server 6.1. 1977: SAMLv2 sample configure.jsp files fail on WebSphere Application Server 6.1On a WebSphere Application Server 6.1 instance, the /sample/saml2/sp/configure.jsp and /sample/saml2/idp/configure.jsp files fail to compile. The configure.jsp files require JDK 1.5, but the JDK source level for JSP files is set to JDK 1.3 on WebSphere Application Server 6.1. Workaround: Edit the JSP engine configuration parameters to set the JDK source level to 1.5:
For more information about the jdkSourceLevel parameter as well as other JSP engine configuration parameters, see: Web Services Security (WSS) Issues4057: Dynamic web service provider configuration with endpoint does not take effectIf you set up the proxy use case based on the loan sample for Web Services Security (WSS) and create two web service providers (WSP) with profile names other than wsp, an error occurs. Workaround. For JAX-WS/web application based web services, use the static point end as the WSP name to support multiple web services. For EJB based web services, use the default WSP configuration. Access Manager SDK (AMSDK) Issues4139: With OpenSSO configured with AMSDK plug-in, session service assigned to a new role has conflict resolution level attribute issueWith OpenSSO Enterprise configured with the Access Manager SDK (AMSDK) plug-in, the session service assigned to a new role has a conflict resolution level attribute issue. Changing the conflict resolution level doesn't take effect on a user assigned with the role. Workaround: Replace the cospriority attribute using a utility such as ldapmodify. For example: ldapmodify -p 50389 -h dshost -D"cn=directory manager" -w dmpassword -c -f /tmp/mod where /tmp/mod is: dn:cn="cn=sfo1,dc=opensso,dc=java,dc=net",cn=iPlanetAMSessionService,dc=opensso,dc=java,dc=net changetype:modify replace:cospriority cospriority:4 Upgrade, Compatibility, and Coexistence Issues
4108: Incorrect encryption key used after configuring OpenSSO Enterprise against existing schema (DIT)After configuring OpenSSO Enterprise against an existing schema (DIT) , you cannot log in to the console, because the encryption key entered during the configuration (the one from the old Access Manager or Federation Manager instance) is not used. Instead, a new incorrect encryption key is generated, which creates an incorrect serverconfig.xml file. Workaround.
3962: Incorrect Console URL returned after authentication for non-admin userIf OpenSSO is configured with an Access Manager 7.1 Directory Server schema (DIT) in coexistence mode and a non-admin user logs in to the OpenSSO Console, the user is taken to an invalid URL. For example: http://ssohost.example.com:8080/amserver/..amserver/base/AMAdminFrame. Workaround. Edit the URL as follows: protocol://host.domain:port/deploy_uri/idm/EndUser For example: http://ssohost.example.com:8080/amserver/idm/EndUser 3961: amadmin cannot log in to OpenSSO Console in coexistence modeIf OpenSSO is configured with an Access Manager 7.1 Directory Server schema (DIT) in coexistence mode, an attempt to log in as amadmin to the Console using LDAP authentication fails. Workaround. To log in as amadmin to the OpenSSO Console in coexistence mode, add the module=DataStore query parameter. For example: protocol://host.domain:port/deploy_uri/UI/Login/?module=DataStore For example: http://ssohost.example.com:8080/amserver/UI/Login/?module=DataStore 2348: Document Distributed Authentication UI server supportThe OpenSSO Enterprise Distributed Authentication UI server component works only with OpenSSO Enterprise. The following scenarios are not supported:
830: ID-FF schema metadata is not backward compatibleIf you are upgrading from a previous release of Access Manager or Federation Manager to OpenSSO Enterprise 8.0, ID-FF profiles do not work unless you also upgrade the Access Manager or Federation Manager schema. Workaround. Before you try the ID-FF profiles, upgrade the Access Manager or Federation Manager schema. For more information about upgrading the schema, see the Sun OpenSSO Enterprise 8.0 Upgrade Guide. Policy Agents Issues3581: Policy evaluation with DNS condition fails for version 3.0 policy agentsFor the version 3.0 policy agent for Sun Java System Application Server or Glassfish Application Server, policy evaluation with a DNS condition fails, because by default, the ServletRequest.getRemoteHost method returns an IP address instead of a host name. Workaround. Change the default behavior by setting the following property in the Application Server or Glassfish domain.xml file: dns-lookup-enabled="true" Or, if you prefer, set this property in the Application Server or Glassfish Admin console. Internationalization Issues
4090: Non-English entitlements are garbledWorkaround: To view the localized entitlements, which are provided in .txt format, use a browser with the encoding specified for each locale in the browser as follows:
4051: Multi-byte trusted partner name is garbled in ConsoleIn the OpenSSO Console, if you go to Federation > SAML1.x Configuration, and then create a new Trusted Partner with a multi-byte Name in the Common Settings section, the trusted partner name is garbled. 3993: End user page shows question marks for CCK and JA localesOn the Geronimo web container in CCK and JA locales, if you log in as a user other than amadmin, the Access Control, realm, General, EndUser page (http://host:port/deployuri/idm/EndUser) shows question marks. 3976: Online Help “Tips on Searching” shows 404 error in non-English localeIf you log in to the OpenSSO Console in a non-English locale such as French, click Help, and then “Tips on Searching”, the right Help panel shows a 404 error. Workaround. To view “Tips on Searching” in English, set the browser language to English and then refresh the online Help window 3766: encode.jsp and ampassword -e differ with multi-byte (non-ASCII) charactersIf a password file contain multi-byte (non-ASCII) characters, the ampassword utility does not return the correct encrypted value. However, encode.jsp does return the correct value. Workaround. If you are using ampassword, use a password file that contain only ASCII characters. If the password contains multi-byte characters, use encode.jsp to encrypt the password:
3763: Some non-ASCII characters are garbled when the web container is in C localeIf you start the web container in the C locale and set your browser to a language such as French, after you log in to the Admin Console, some characters are garbled. 3713: Password reset page is not localized for CCJK localesFor CCJK locales, the password reset page (http://host:port/deployuri/password) is not localized. 3590: Change location for dounix_msgs.po filesThe dounix_msgs.po files for the Unix authentication module have not been translated because the Unix authentication module will not be included in a future OpenSSO Enterprise release. See Deprecation Notifications and Announcements. 1793: Authentication fails with multi-byte character for org or module in query parameterIf you try to log in to the OpenSSO Console using the org or module parameter with characters that are not UTF-8, the login fails. For example: http://host:port/deployuri/UI/Login?module=Japanese-string&gx_charset=UTF-8 Workaround. Use UTF-8 URLencoding characters such as %E3%81%A6 instead of native characters. Localization Issues
4017: In Spanish locale, “2.2 Agents” is translated only as Agentes in ConsoleIf the OpenSSO Console is in the Spanish locale, the 2.2 is missing from the translation of “2.2 Agents”. 3994: In Spanish locale, cannot access Certificate for Configuration > AuthenticationIf the OpenSSO Console is in the Spanish locale, clicking Configuration, Authentication, and then Certificate returns an error. 3971: In Chinese (zh_CN) locale, online help is in EnglishIn the Chinese (zh_CN) locale. the Console online help text is displayed in English rather than Chinese. If you set your browser preferred language to zh_CN, only the online help text in the left tree will be English. If you set your browser preferred language to zh, all online help text will be English. Workaround. Copy the zh_CN online Help contents to a new zh directory in the web container's webapps directory and the restart the web container. For example for Apache Tomcat, copy /Tomcat6.0.18/webapps/opensso/html/zh_CN/* to a new directory named /Tomcat6.0.18/webapps/opensso/html/zh/. And then restart the Tomcat container. 3802: Problems in the French part of copyright noticeIn the French part of the English copyright notice, “Etats-unis” is missing an accent, a space is missing after the comma at “armes nucléaires,des missiles”, and spaces should not be in “Etats - Unis”. Upgrading to OpenSSO Enterprise 8.0Upgrading to OpenSSO Enterprise 8.0 is supported from the following releases:
The upgrade process includes upgrading an existing Access Manager or Federation Manager server instance and the corresponding configuration data stored in Sun Java System Directory Server. For the detailed upgrade steps, see the Sun OpenSSO Enterprise 8.0 Upgrade Guide. Deprecation Notifications and Announcements
How to Report Problems and Provide FeedbackIf you have questions or issues with OpenSSO Enterprise, contact Sun Support Resources (SunSolve) at http://sunsolve.sun.com/. This site has links to the Knowledge Base, Online Support Center, and Product Tracker, as well as to maintenance programs and support contact numbers. If you are requesting help for a problem, please include the following information:
Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments and suggestions. Go to http://docs.sun.com/ and click Feedback. Provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title is Sun OpenSSO Enterprise Release Notes and the part number is 820-3745. Additional Sun ResourcesYou can find additional useful information and resources at the following locations:
Accessibility Features for People With DisabilitiesTo obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. For information about Sun's commitment to accessibility, visit http://sun.com/access. Related Third-Party Web SitesThird-party URLs are referenced in this document and provide additional, related information. Note – Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources. Revision HistoryTable 10 Revision History
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||