![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[z/OS]](../images/ngzos.gif)
Interoperating with a C++ common object request broker architecture client
WebSphere® Application Server supports security in the CORBA C++ client to access-protected enterprise beans. If configured, C++ CORBA clients can access protected enterprise bean methods using a client certificate to achieve mutual authentication on WebSphere Application Server applications.
About this task
You can achieve interoperability
of Security Authentication Service between the C++ Common Object Request
Broker Architecture (CORBA) client and WebSphere Application Server using Common Secure
Interoperability Version 2 (CSIv2) authentication protocol over Remote
Method Invocation over the Internet Inter-ORB Protocol (RMI-IIOP).
The CSIv2 security service protocol has authentication, attribute
and transport layers. Among the three layers, transport authentication
is conceptually simple, however, cryptographically based transport
authentication is the strongest. WebSphere Application Server has implemented
the transport authentication layer, so that C++ secure CORBA clients
can use it effectively in making CORBA clients and protected enterprise
bean resources work together.
![[z/OS]](../images/ngzos.gif)
For more
information, see Configurações de segurança global.
Security authentication from non-Java based C++ client to enterprise beans. WebSphere Application Server supports security in the CORBA C++ client to access-protected enterprise beans. If configured, C++ CORBA clients can access protected enterprise bean methods using a client certificate to achieve mutual authentication on WebSphere Application Server applications.
- Create an environment file for the client, such as current.env.
Set the variables presented in the following list in the file:
Table 1. Environment Variables. This table lists the environment variables needed to support the C++ CORBA client in accessing protected enterprise beans.
C++ security setting Description client_protocol_password Specifies the password for the user ID. client_protocol_user Specifies the user ID to authenticate at the target server. security_sslKeyring Specifies the name of the RACF® keyring for the client to use. The keyring must be defined under the user ID that is issuing the command to run the client. - Point to the environment file using the fully qualified path name
through the WAS_CONFIG_FILE environment variable. For example, in
the test.sh test shell script, export:
Some of the environment file terms are explained here:/WebSphere/V6R0M0/DeploymentManager/profiles/default/config/cells /PLEX1Network/nodes/PLEX1Manager/servers/dmgr
- default
- profile name
- PLEX1Network
- cell name
- PLEX1Manager
- node name
- dmgr
- server name
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)