Skip to main content

Does Security work on POAs with MAIN_THREAD_MODEL policy?

  • February 16, 2013
  • 0 replies
  • 0 views

Problem:

  • Product Name: Visibroker
  • Product Version: 6.5
  • Product Component: SSL
  • Platform/OS Version: All

In the bank_ssl example that is shipped with Visibroker, if POA ThreadPolicy is changed to MAIN_THREAD_MODEL, the client fails saying that it cannot access insecure server. After doing a printIOR, it was found out that the SSL components are missing in the ior if the POA thread policy is MAIN_THREAD_MODEL. Is this a known limitation of MAIN_THREAD_MODEL ?

Resolution:

The iiop_tm Server engine is not included with the security by default. Please start the secure server with main thread model with the following properties.


# Setting SSL Layer Attributes
vbroker.security.peerAuthenticationMode=require_and_trust
vbroker.security.trustpointsRepository=Directory:./trustpoints

vbroker.se.iiop_tm.scms=iiop_tm,ssl
vbroker.se.iiop_tm.scm.ssl.manager.type=Socket
vbroker.se.iiop_tm.scm.ssl.manager.connectionMax=0
vbroker.se.iiop_tm.scm.ssl.manager.connectionMaxIdle=0
vbroker.se.iiop_tm.scm.ssl.listener.type=SSL
vbroker.se.iiop_tm.scm.ssl.listener.port=0
vbroker.se.iiop_tm.scm.ssl.listener.proxyPort=0
vbroker.se.iiop_tm.scm.ssl.dispatcher.type=MainThread
vbroker.se.iiop_tm.scm.ssl.dispatcher.threadMin=0
vbroker.se.iiop_tm.scm.ssl.dispatcher.threadMax=0
vbroker.se.iiop_tm.scm.ssl.dispatcher.threadMaxIdle=0
vbroker.se.iiop_tm.scm.ssl.dispatcher.coolingTime=3
vbroker.se.iiop_tm.scm.ssl.dispatcher.threadStackSize=0


#Security
#VisiBroker