PI28207: SECJ0395E: COULD NOT LOCATE THE SECURITY SERVER HOST AND PORT

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere Application Server Network Deployment and
standalone client, unable to locate the Security
Server Host/port even when defined in the sas.client.props
file. Getting exception:

com.ibm.websphere.security.auth.AuthenticationFailedException:
SECJ0395E: Could not locate the SecurityServer at host/port:{0}
to validate the userid and password entered. You might need to
specify valid securityServerHost/Port in
${WAS_INSTALL_ROOT}/profiles/profile_name/properties/sas.client.
props file.
at
com.ibm.ws.security.auth.ContextManagerImpl.getSecurityServer(Co
ntextManagerImpl.java:2278)
at
com.ibm.ws.security.auth.ContextManagerImpl.access$400(ContextMa
nagerImpl.java:380)
at
com.ibm.ws.security.auth.ContextManagerImpl$10.run(ContextManage
rImpl.java:4500)
at
com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
Impl.java:5395)
at
com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(Conte
xtManagerImpl.java:5463)
at
com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManager
Impl.java:4498)
at
com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManager
Impl.java:4310)
at
com.ibm.ws.security.common.auth.module.WSLoginModuleImpl.login(W
SLoginModuleImpl.java:423)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who migrate Java client from         *
*                  WebSphere Application Server v6.0           *
****************************************************************
* PROBLEM DESCRIPTION: In client program, configuration        *
*                      specified in sas.client.props is        *
*                      not honored until ORB is initialized    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a client program is invoked with WebSphere Application
Server v7 and above, security configuration specified in
sas.client.props is loaded when ORB is initialized.
Prior to loading sas.client.props, default security
configuration is applied and enforce security.  This may cause
unexpected failure.
For example, when security is disabled in
sas.client.props, until ORB is initialized in the client
program, default security configuration (security enabled) is
applied.

Problem conclusion

The following property is introduced with this apar

Custom property:
   com.ibm.websphere.security.config.client.init
Value:

true : Enables apar code. WebSphere will read
sas.client.props at the very beginning of the java
client startup.

false: Default.  WebSphere reads sas.client.props at the
time of ORB initialization.

At the invocation of Java client, the custom property can
be specified as follows to enable apar code :
 -Dcom.ibm.websphere.security.config.client.init=true
along with
 -Dcom.ibm.CORBA.ConfigURL="file:c:/xxx/sas.client.props

Note:
WebSphere Application Server v6.0, if sas.client.props is not
specified at the time of client invocation, the
Application server takes it as "security disabled"

At WebSphere Application Server v6.1 and above, if
sas.client.props is not specified at the time of client
invocation, the Application server takes it as "security
enabled" and apply default security settings for client.

To disable security in client from startup,  apply this apar
and configure sas.client.props with
   com.ibm.CORBA.securityEnabled=false
and specify both custom properties (
-Dcom.ibm.websphere.security.config.client.init=true and
-Dcom.ibm.CORBA.ConfigURL="file:c:/xxx/sas.client.props)

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.37, 8.0.0.11, 8.5.5.5.  Please refer to
the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI28207
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-22
Closed date
2015-01-06
Last modified date
2015-01-06

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI28207: SECJ0395E: COULD NOT LOCATE THE SECURITY SERVER HOST AND PORT

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?