Secure Remote Access (SRA)

SRA services are not setup when you manually install the sample portals using the command line interface. (#6516280)

Solution:

Manually invoke the following ant targets to setup SRA services for each sample:

• community_sra

• developer_sra

• enterprise_sra

Execute the following command after you install the sample portal.

/usr/sfw/bin/ant -f /opt/SUNWportal/samples/portals/build.xml community_sra developer_sra enterprise_sra -Dconfig.location= input-properties-file-location

In Secure Remote Access, you can add only one row at a time. (#6497988)

Solution:

In SRA screens, when you try to add multiple rows, save the details after you add each row.

Unable to access Unified Web Client (UWC) application through proxylet if UWC and Portal Server are installed on different machines. (#6348935)

Solution:

If UWC application and Portal Server are installed on different machines, do the following to access UWC machine through proxylet:

1. In the Portal Server administration console, enable cookie management in the Gateway profile.

2. In the URLs to which user session cookie is forwarded field, add UWC, Calendar, and Messaging Server urls. For example, add the following: http://port/uwc, http://calhost:calport, http://messaginghost:messagingport.

3. In the AMConfig.properties file of UWC machine, change com.iplanet.am.cookie.name=iPlanetDirectoryPro to com.iplanet.am.cookie.name=iPlanetDirectoryPro1.

   ---

   Note –

   This is to have different cookie names in Gateway and Portal Server machines.

   ---

4. In the UWC machine, using configutil, change the session cookie for Messaging Server to iPlanetDirectoryPro1.

5. Add the UWC, Calendar, and Messaging Server URLs in Non-Authenticated URL list of UWC.

6. Restart Gateway, UWC, and Portal Server.

certadmin ignores nickname while installing a renewed certificate. (#6360869)

Description:

certadmin ignores the nickname while installing a renewed certificate. This results in the gateway picking up the expired certificate, not the new one. It is not possible to distinguish between two certificates with the same nickname.

Solution:

Do any one of the following:

1. Delete the old certificate before importing the new one. Do the following in Portal Server 7.1:

   cd PortalServer_base/SUNWportal/bin/certadmin -n config_name

   Choose 5 to delete the certificate.

2. Do not renew the certificate. When a certificate expires, get a brand new one with the new keys.