How do you set up the admin console to run over https (post-installation)?

Currently the portal software is set up to run the client over https, but we would like to run the admin console over https, as well. This would be post-installation.
[180 byte] By [708882] at [2007-11-25 4:34:50]
# 1

From your definition it looks like you are using gateway and you want to turn on ssl between the gateway and server. If that is the case the description below should help u ..

Turning on SSL after a non-SSL installation

-

1. This can be done only by the super administrator.

2. A set of attributes need to be changed to turn on SSL between the server and

the gateway. They are:

Server Attributes

Gateway Attributes

3. Please follow the steps given below to change required Server Attributes.

3a. From the admin console, choose "Server Management" link.

3b. Click on the "Manage Server profile" link.

3c. Change the "Server Port" attribute to any port number NOT in use.

3d. Choose "https" as the "Server Protocol".

3e. Click on "Submit" and save the changes, a message conveying succesful

update to profile is displayed, click on "Continue".

3f. From the admin console, choose "Server Management" link.

3g. Click on the "Manage Naming profile" link.

3h. Replace the port number in "Profile URL", "Session URL" and "Logging URL"

by the port number specified in step 3c, and change the protocol from

"http" to "https"

eg. if you've specified 443 in step 3c, then for a default port install of

8080, one would need to replace http://<servername>:8080/profileservice

with https://<servername>:443/profileservice for "Profile URL".

3i. Click on "Submit" and save the changes, a message conveying succesful

update to profile is displayed, click on "Continue".

4. Please follow the steps given below to change Gateway Attributes.

4a. From the admin console, choose "Gateway Management" link.

4b. Click on the "Manage Gateway profile" link.

4c. Replace the port number in all the entries in "Forward Cookie URL List"

by the one specified in step 3c, and replace protocol "http" with "https".

4d. Click on "Submit" and save the changes, a message conveying succesful

update to profile is displayed, click on "Continue".

5. update the following values in /etc/opt/SUNWips/platform.conf as described.

if the port number chosen in step 3c is 7070 then change values as follows:

ips.server.protocol=https

ips.server.port=7070

ips.naming.url=https://<servername>:7070/namingservice

ips.notification.url=https://<servername>:7070/notificationservice

6.In case of multiple servers/gateways the above steps need to to be done

for all installations.

7. Obtain a certificate from any of the Certificate authorities supported

by the portal server. Install it with the iWS.

Please refer to section "To generate a certificate for the server

component of the Portal Server product" in Appendix A on pg. 75 of the

installation guide 3.0, and follow steps 1 through 27 to send a CSR to

a CA, install its certificate.

8. Restart all server and gateway instances.

9. All iplanet gateways are now setup to use SSL for communication with

all servers.

Karthik_Krishnamoorthy at 2007-6-29 2:46:21 > top of Java-index,Web & Directory Servers,Portal Servers...