IBM Support

JR56036: THE BPMCONFIG COMMAND DOES NOT SUPPORT SPECIAL CHARACTERS LIKE # AND ^ IN PASSWORDS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When any of the bpm.cell.authenticationAlias.#.password or
    bpm.de.authenticationAlias.#.password properties in the input
    file for the BPMConfig command contains characters other than
    a-z, A-Z, 0-9, !,(,),-,.,_,`,~, or @, the configuration property
     validation fails with an error similar to the following error:
    
    CWMCB0368E: The property bpm.de.authenticationAlias.1.password
    has an invalid value [bpm<admin>] because bpm<admin> contains
    invalid characters <>. The valid characters list is
    a-zA-Z0-9!()-._`~@.
    

Local fix

Problem summary

  • Validation of password properties was introduced in IBM BPM 8.5
    to avoid problems that special characters cause. However, this
    new validation code rejects passwords that worked in IBM BPM
    V8.0.1, which causes problems when you are migrating.
    In IBM BPM V8.5.7 cumulative fix 2016.09, a new
    -omitPasswordValdation parameter will be added to the BPMConfig
    command that you can use to omit the password validation.
    
    Note: Using this parameter might cause argument-processing
    errors of the various commands that BPMConfig invokes behind the
    scenes. Alternatively, you might not see a processing error, but
    some characters will be lost and the actual password that is
    stored will not be what you specified in the properties file.
    

Problem conclusion

Temporary fix

  • If possible, configure the IBM BPM deployment environment by
    using a password that contains only supported characters, and
    then manually change the password after IBM BPM is configured.
    

Comments

APAR Information

  • APAR number

    JR56036

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    857

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-31

  • Closed date

    2016-08-15

  • Last modified date

    2016-08-15

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

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

Fix information

Applicable component levels

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 August 2016