Sun Crypto Accelerator 1000

Does Portal Server 3 support the SCA1000 board?Documentation only mentions Apache and IPlanet WS.Note: Sun just released a patch ( 112869-02 ) to upgrade the board to use OpenSSL 0.9.6e but Portal Server 3 doesn't appear to use OpenSSL
[264 byte] By [706901] at [2007-11-25 8:10:17]
# 1

Answer from Portal Server Tech support: No, only Apache and Iplanet Web Server can take advantage of the Sun Crypto Accelerator 1000 (SCA1000)

Personal Recommendation Don't bother buying Portal Server 3 if you plan on using the amazingly fast SCA1000.

Apache compiled with Sun's own version of OpenSSL or Iplanet WS will work and the speed will be worth it.

706901 at 2007-7-1 14:03:42 > top of Java-index,Web & Directory Servers,Portal Servers...
# 2

Portal users iPlanet Web Server as its servlet container to server all the servlets so there is a possibility that it might work. If your using the gateway then the ssl libraries are different versions from the web server libraries. Portal 3.0 has not been tested with Sun Crypto Accelerator 1000 (SCA1000) and hence compatibility is a question there. Also we have not had many requests to support or test SCA 1000.

Karthik_Krishnamoorthy at 2007-7-1 14:03:42 > top of Java-index,Web & Directory Servers,Portal Servers...
# 3

Kathy,

Thanks for replying. I was wondering how much of Iplanet is in Portal Server .Is it subject to the same vulnerablities like iPlanet (Sun ONE) Web Server chunked transfer encoding heap buffer overflow ?http://www.iss.net/security_center/static/9799.php

Supposedly if I install the latest 4.1 SP11 it may break Portal Server.

Also is there any advantage to running the Gateway if I only have one server? The docs say it is possible to run both on the same machine but what will I miss out on if I don't use the Gateway.

706901 at 2007-7-1 14:03:42 > top of Java-index,Web & Directory Servers,Portal Servers...
# 4
whoops, Kathy? where did that name come from. Of course I meant Karthic - you've already been more helpful than Sun's paid support. Thanks
706901 at 2007-7-1 14:03:42 > top of Java-index,Web & Directory Servers,Portal Servers...
# 5

The way portal is made is constructed is, it is bunch of services that sit on top of the web server. It uses the servlet container of the web server to execute the servlets. For jsp channels portal uses its own jsp engine.

The services are basically profile, auth, session, logging, notification and naming. Portal uses a combination of jndi and ldap api to talk to the directory server to fetch the content and uses its own cache algorithms to maintain and update and keep the profile cache in sync with multiple profile servers ( from sp3 hp2 onwards).

In the past bugs fixed in the web server service packs affect portals code specifically if the fixes are related to the servlet containers or the http functionality that portal uses.

From what I am aware of about this problem, the product is testing with sp 11 of the web server to make sure that upgrading to the latest web server service pack does not break anything in portal. I don't know the time line for which this test would be completed but I assuming it would be in the next few weeks.

The gateway is basically used for securing the portal server, it provides rewriting functionality as well as netlet functionality. A gateway deployment architecture would have the gateway sitting in a different system other portal server ( in most cases this would be the dmz) and then there would be a firewall betweeen the portal server and the gateway.

HTH ..

Karthik_Krishnamoorthy at 2007-7-1 14:03:42 > top of Java-index,Web & Directory Servers,Portal Servers...