Manuel d'utilisation / d'entretien du produit 819468310 du fabricant Sun Microsystems
Aller à la page of 36
Sun Ja va S y stem A c cess Manager 7.1 Release Notes Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part N o: 819–4683–10 March 2007.
Copyright 2007 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. I n particular, and without limitation, these intellectual property rights may include one or more U.
Cont ents Sun Java S ystem A ccess Manager 7.1 Release Notes .......................................................................5 Revision History ....................................................................................................
AMSDK I ssues .............................................................................................................................. 27 SSL Issue .................................................................................................
Sun Java S ystem Ac cess Manager 7.1 Release Not es March 2007 Part N umber 819-4683-10 The Sun J ava TM System Access M anager 7.1 Release Notes contain important information available for the Sun J ava Enterprise System ( J ava ES) release, including new Access M anager features and known issues with workarounds, if available.
Revision History The following table shows the A ccess Manager 7.1 Release N otes revision history. T ABLE 1 Revision History Date Description of Changes J uly 2006 Beta release. March 2007 Java Enterprise System 5 release About Sun Ja va S yst em Ac cess Manager 7.
devices, applications, and service-driven networks. Typical uses of the JMX technology include: consulting and changing application conguration, accumulating statistics about application behavior, notication of state changes and erroneous behaviors.
■ N umber of successful authentications ■ N umber of failed authentications ■ N umber of successful logout operations ■ N umber of failed logout operations ■ Transaction time for each module if possible (running and waiting states) 2.
■ A new policy condition AuthenticateToRealmCondition added, to enforce the user is authenticated to a specic realm. ■ A new policy condition LDAPFilterCondition is added, to enforce the user matches the specied ldap lter.
■ Support JCE Based SecureLogHelper - making it possible to use JCE (in addition to JSS) as a security provider for Secure Logging implementation Deprecation Notication and Announcement Sun J ava(TM) System Access M anager 7.
T ABLE 2 Hardware and Software Requirements Component Requirement Operating system (OS) ■ Solaris TM 10 on SP ARC, x86, and x64 based systems, including support for whole root local and sparse root zones. ■ Solaris 9 on SP ARC and x86 based systems.
T ABLE 2 Hardware and Software Requirements (Continued) Component Requirement Web containers Sun Java System Web Server 7.0 On supported platform/OS combinations you may elect to run the Web Server instance in a 64 bit JVM. Support platforms: Solaris 9/SP ARC, Solaris 10/SP ARC, Solaris 10/AMD64, Red Hat AS or ES 3.
T ABLE 3 Supported Browsers (Continued) Browser Platf orm Mozilla TM 1.7.12 Solaris OS, versions 9 and 10 Windows XP Windows 2000 Red Hat Linux 3 and 4 M a cO SX Netscape TM Communicator 8.
Ac cess Manager Legacy Mode If you are installing A ccess Manager with any of the following products, you must select the A ccess Manager Legacy (6.x) mode: ■ Sun J ava System Portal Server ■ Sun .
“ Congur e Later” Installa tion Option If you ran the J ava ES Installer with the “Congure Later“ option, you must run the amconfig script to congure A ccess Manager after installation. To select Legacy (6.x) mode, set the following parameter in your conguration script input le ( amsamplesilent ): .
Known Issues and Limita tions This section describes the following known issues and workarounds, if available, at the time of the A ccess Manager 7.1 release.
■ “Incompatibilities exist in core authentication module for legacy mode (6305840)” on page 18 ■ “Delegated Administrator commadmin utility does not create a user (6294603)” on page 18 ■.
Incompatibilities e xist in core authentication module f or legac y mode (6305840) A ccess Manager 7.1 legacy mode has the following incompatibilities in the core authentication module from A ccess Manager 6 2005Q1: ■ Organization A uthentication M odules are removed in legacy mode.
C onguration Issues ■ “Notication URL needs to be updated for A ccess Manager SDK installation without web container (6491977)” on page 19 ■ “Password Reset service reports noticati.
Platform server list and FQDN alias a ttribute are not updated (6309259, 6308649) In a multiple server deployment, the platform server list and FQD N alias attribute are not updated if you install A ccess Manager on the second (and subsequent) servers.
Default Ac cess Manager mode is realm in the congur ation state le templat e (6280844) By default, the A ccess Manager mode (AM_REALM variable) is enabled in the conguration state le template.
Console does not r eturn the results set from Directory S er ver after reaching the resour ce limit (6239724) Install Directory Server and then A ccess Manager with the existing D IT option. Login to the A ccess Manager Console and create a group. Edit the users in the group.
5. Click Save. SDK and Client Issues ■ “Clients do not get notications after the server restarts (6309161)” on page 23 ■ “SDK clients need to restart after service schema change (6292616)” on page 23 Clients do not get notications after the ser ver restarts (6309161) A pplications written using the client SDK ( amclientsdk.
2. In Directory Server console , add the following A CI. dn:ou=1.0,ou=SunAMClientData,ou=ClientData,<ROOT_SUFFIX> changetype:modifyadd:aci aci: (target="ldap:///ou=1.0,ou=SunAMClientData,ou=ClientData,<ROOT_SUFFIX>") (targetattr = "*"(version 3.
List. If you create two new organizations with the same name, the operation fails, but A ccess Manager displays the “organization already exists” message rather than the expected “attribute uniqueness violated” message. Workaround: None. I gnore the incorrect message.
if you are using a third-party web container (IBM WebSphere or BEA WebLogic Server) and the optional HttpSession , you might need to limit the web container's maximum HttpSession time limit to avoid performance problems.
AMSDK Issues ■ “Error displayed when performing AMI dentity.modifyService (6506448)” on page 27 ■ “Group members don't show up in selected list (6459598)” on page 27 ■ “A ccess Ma.
Ac cess Manager Login URL Returns Message " No such Organiza tion found " (6430874) The problem may be due to the use of mixed-case (both uppercase and lowercase) characters in the fully qualied domain name (FQDN). Example: HostName.PRC.Example.
The amcong script fails when SSL c er ticate is expir ed. (6488777) If the A ccess Manager container is running in SSL mode, and the container SSL certicate is expired, amconfig fails and may cause classpath corruption.
JVM problems occur when running A ccess Manager on Application Ser ver (6223676) If you are running A pplication Server 8.1 on Red Hat Linux, the stack size of the threads created by the Red Hat OS for A pplication Server is 10 Mbytes, which can cause JVM resource problems when the number of A ccess Manager user sessions reaches 200.
F ederation fails when using Artifac t prole (6324056) If you setup an identity provider (IDP) and a service provider (SP), change the communication protocol to use the browser Artifact prole, and then try to federate users between the IDP and SP , the federation fails.
P olic y condition date must be specied ac cording to English cust om (6390856) P olicy condition date format labels under the Chinese locale are not displayed according to Chinese customs. Labels are proposing a date format like English date format.
Documentation Issues ■ “Document the roles and ltered roles support for LD APv3 plug-in (6365196)” on page 33 ■ “Document unused properties in the AMConfig.
5. If you are using a JDK version earlier than JD K 1.5, edit the jdk_root /jre/lib/security/java.security le and add Bouncy C astle as one of the providers. For example: security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider 6. Set the following property in the AMConfig.
How t o Repor t Problems and Pr ovide F eedback If you have problems with A ccess Manager or Sun J ava Enterprise System, contact Sun customer support using one of the following mechanisms: ■ Sun Support Resources (SunSolve) services at http://sunsolve.
Ac cessibility F eatures for P eople W ith Disabilities To 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.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté Sun Microsystems 819468310 c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du Sun Microsystems 819468310 - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation Sun Microsystems 819468310, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le Sun Microsystems 819468310 va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le Sun Microsystems 819468310, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du Sun Microsystems 819468310.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le Sun Microsystems 819468310. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei Sun Microsystems 819468310 ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
