Problem:
Product Name; VisiBroker
Product Version: 5.2.1 and above
Product Component: Security
Platform/OS : All
JDK: 1.3.1 and above
When the Gatekeeper or VB Server started with security enabled properties (i.e. "vbroker.security.disable=false" and "org.omg.PortableInterceptor.ORBInitializerClass.com.borland.security.core.Init=1") , the generated IOR information looks strange (a port 0 for communication ?):
E.g.:
Interoperable Object Reference:
Type ID: IDL:inprise.com/gatekeeper/AliasManager:1.0
Contains 1 profile.
Profile 0-IIOP Profile:
version: 1.2
host: 143.186.181.150
port: 0
......
But when Gatekeeper or VB Server used the default properties, the IOR looks OK.
Resolution:
It is an expected behavior. Basically, it is a security service related issue.
Firstly, display of IIOP port as 0 is recommended by OMG for secured servers. It is done so to avoid exposing the IIOP port from hackers. Please refer to OMG-CSIv2 specifications for that matter.
Secondly, the Client program can set the property "vbroker.orb.alwaysSecure" on the Client to avoid trying to connect to port 0 in the IIOP profile. In fact, the IOR contains full information about the IIOP port, SSL components, etc, but it is hidden from the users.
Set the following properties on VB Server or Gatekeeper (when these are started with security enabled), and see the difference. Here are the available options, you need to select one:
vbroker.security.secureTransport= true | false
vbroker.security.server.transport= SECURE_ONLY | CLEAR_ONLY | ALL
If "vbroker.security.secureTransport=true" is set, then by default, "vbroker.security.server.transport=SECURE_ONLY" is set, which means the IIOP port in the IOR will be displayed as 0.
#IOR
#Security
#CSIV2
#printIOR
#VisiBroker
