PM75115: RE-ENABLING SECURITY WITH WSADMIN DOES NOT UPDATE PASSWORD IF THE USER ALREADY EXISTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • While using wsadmin to activate administrative security it was
    found that if security was re-enabled that the password of the
    administrator is not properly set if the user already exists.
    
    Example reproduction
    1) WebSphere security is off in a new cell.
    
    2) WebSphere security is enabled with
    $AdminTask applyWizardSettings [list -secureApps false -
    secureLocalResources false -ignoreCase false -userRegistryType
    WIMUserRegistry -adminName user -adminPassword password]
    
    3) WebSphere security is disabled with
    $AdminTask setGlobalSecurity [list -enabled false]
    
    4) Now security is enabled again with the same user name but
    different a password:
    $AdminTask applyWizardSettings [list -secureApps false -
    secureLocalResources false -ignoreCase false -userRegistryType
    WIMUserRegistry -adminName user -adminPassword PASS]
    
    The problem is that the admin user still uses the old password
    "password" from step 2 instead of updating the password to
    what was given in step 4.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who use "applyWizardSettings" to     *
    *                  set                                         *
    *                  adminPassword for Federated Repository      *
    ****************************************************************
    * PROBLEM DESCRIPTION: "applyWizardSettings" command fails to  *
    *                      update password when it is issued for   *
    *                      existing admin user.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The command did not update the password if it is already set.
    The code has been corrected to update the password.
    Note: The issue is specific to admin account in the
    default FileRegistry for Federated Repository. Also this
    command does not support ldap/custom registries that are
    plugged into Federated Repository.
    

Problem conclusion

Temporary fix

  • After "applyWizardSettings" command was issued, if password was
    still not updated, use "changeFileRegistryAccountPassword"
    command.
    

Comments

APAR Information

  • APAR number

    PM75115

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-16

  • Closed date

    2013-03-20

  • Last modified date

    2013-10-14

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
General

Software version:

7.0

Reference #:

PM75115

Modified date:

2013-10-14

Translate my page

Machine Translation

Content navigation