What is the Orbix 6.3 configuration variable plugins:atli2_tls:use_jsse_tk used for?

Dominique Sacre · 2013-05-17T17:44:00+00:00

Summary This article provides background information on the usage of the plugins:atli2_tls:use_jsse_tk Orbix configuration variable. Article Number 28237 Environment Orbix 6.3.5 All Supported Operating Systems Question/Problem Description What is the Orbix 6.3 configuration variable plugins:atli2_tls:use_jsse_tk used for?What is the impact of changing the Orbix 6.3 configuration variable plugins:atli2_tls:use_jsse_tk? Clarifying Information In Orbix 6.3.5, the OpenSSL toolkit is the default TLS toolkit for C applications and the JDK JCA/JSSE toolkit is the default TLS toolkit for Java applications.Since Orbix 6.3.5, when you deploy a new domain, Orbix explicitly sets the plugins:atli2_tls:use_jsse_tk variable to "true". Error Message Defect/Enhancement Number Cause Resolution This configuration variable specifies whether or not to use the JSSE/JCE architecture with Orbix Java applications.This value has been added by default to enable JCE/JSSE toolkit on new Orbix 6.3.5 deployments.If set to true, Orbix uses the JSSE/JCE architecture to implement SSL/TLS security.If set to false, Orbix uses the Baltimore SSL/TLS toolkit.If this configuration variable is not explicitly set, it defaults to "false" (same as in previous Orbix releases), with the effect that Baltimore toolkit is used. However, removing this variable is not recommended, since the Baltimore toolkit will be removed in a future release.For further details please see the following documentation:Orbix 6.3.5, Release NotesOrbix Security GuideOrbix 6.3 documentation can be found at:http://supportline.microfocus.com/productdoc.aspx (Please select the product family "CORBA Middleware" and product "Orbix 6") Workaround If the Baltimore toolkit needs to be used by default in new Orbix 6.3.5 deployments this can be achieved by patching the <IT_PRODUCT_DIR>\\asp\\6.3\\etc\\conf\\core.xml file to change the use_jsse_tk to false. This would reenable Baltimore, just like in Orbix 6.3.4 and prior releases, and would not require to modify generated deployment descriptors. Notes The Baltimore toolkit for Orbix C and Java is now deprecated, and will be removed in a future release. Attachment Created date: 01 February 2012 Last Modified: 13 February 2013 Last Published: 12 May 2012 First Published date: 01 February 2012 #KnowledgeDocs#Orbix

Summary	This article provides background information on the usage of the plugins:atli2_tls:use_jsse_tk Orbix configuration variable.
Article Number	28237
Environment	Orbix 6.3.5 All Supported Operating Systems
Question/Problem Description	What is the Orbix 6.3 configuration variable plugins:atli2_tls:use_jsse_tk used for? What is the impact of changing the Orbix 6.3 configuration variable plugins:atli2_tls:use_jsse_tk?
Clarifying Information	In Orbix 6.3.5, the OpenSSL toolkit is the default TLS toolkit for C applications and the JDK JCA/JSSE toolkit is the default TLS toolkit for Java applications. Since Orbix 6.3.5, when you deploy a new domain, Orbix explicitly sets the plugins:atli2_tls:use_jsse_tk variable to "true".
Error Message
Defect/Enhancement Number
Cause
Resolution	This configuration variable specifies whether or not to use the JSSE/JCE architecture with Orbix Java applications. This value has been added by default to enable JCE/JSSE toolkit on new Orbix 6.3.5 deployments. If set to true, Orbix uses the JSSE/JCE architecture to implement SSL/TLS security. If set to false, Orbix uses the Baltimore SSL/TLS toolkit. If this configuration variable is not explicitly set, it defaults to "false" (same as in previous Orbix releases), with the effect that Baltimore toolkit is used. However, removing this variable is not recommended, since the Baltimore toolkit will be removed in a future release. For further details please see the following documentation: Orbix 6.3.5, Release Notes Orbix Security Guide Orbix 6.3 documentation can be found at: http://supportline.microfocus.com/productdoc.aspx (Please select the product family "CORBA Middleware" and product "Orbix 6")
Workaround	If the Baltimore toolkit needs to be used by default in new Orbix 6.3.5 deployments this can be achieved by patching the <IT_PRODUCT_DIR>\\asp\\6.3\\etc\\conf\\core.xml file to change the use_jsse_tk to false. This would reenable Baltimore, just like in Orbix 6.3.4 and prior releases, and would not require to modify generated deployment descriptors.
Notes	The Baltimore toolkit for Orbix C and Java is now deprecated, and will be removed in a future release.
Attachment

Created date:	01 February 2012
Last Modified:	13 February 2013
Last Published:	12 May 2012
First Published date:	01 February 2012

#KnowledgeDocs
#Orbix

Sign up

Please log in or register:

Welcome to the Rocket Forum!

Please log in or register:

Scanning file for viruses.

This file cannot be downloaded