IBM Support

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

Fixes are available

7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI28207

Modified date: 06 January 2015