IBM Support

LI82469: V5 TO V10 MIGRATION: UNABLE TO CREATE USER WITH USERNAME STARTING FROM 0

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • v5 to v10 migration: Unable to create user with username
    starting from 0
    
    Edit Subject
    
    DescriptionWhile trying to migrate, we noticed that we are
    unable to migrate users whose name start with 0. Please note
    that this is a valid name as we use employee id as username as
    few users have 0 in their employee id as the starting digit.
    Error log:
    
    ERRO[2021-10-12T16:19:26+01:00] unable to create User 0xxxxxx
    ERRO[2021-10-12T16:19:26+01:00] 0354846: name is of incorrect
    type. Expected: string, Given: integer (context: (root).name,
    line: 4, col: 7)
    ERRO[2021-10-12T16:19:26+01:00] 0354846: title is of incorrect
    type. Expected: string, Given: integer (context: (root).title,
    line: 5, col: 8)
    ERRO[2021-10-12T16:19:26+01:00] 0354846: username is of
    incorrect type. Expected: string, Given: integer (context:
    (root).username, line: 9, col: 11)
    ERRO[2021-10-12T16:19:26+01:00] 0354846: Error validating the
    response body against definition '#/components/schemas/User
    
    
    Command used to run ./apicm archive:push pox-mgmt-admin-apic.xx
    xx-p166-dev-001-7646837b80d72eccf5563ba9a8exxxxx-i000.eu-gb.con
    tainers.appdomain.cloudcloud/admin-org/ --saveInfoLog='admin-org
    --saveErrorLog='admin-org-push-try1-error.log'
    --saveDebugLog='admin-org-push-try1-debug.log'
    
    Expected: User to be created.
    

Local fix

Problem summary

  • <span style="background-color:rgb(255, 255, 255)">If the
    username is sent starting with starts with 0 (zero) followed by
    non-zero characters, during internal conversion from YAML to
    JSON, the string data was being read as an integer. This would
    have affected all data values for String fields when value
    begins with zero followed by alphabets, and YAML data is
    sent.</span>
    

Problem conclusion

  • The internal transformation of YAML to JSON, and back to YAML
    was fixed so that we don't convert from String to integer value
    if quoted.
    
    The fix was done in LTS 10.0.1.6 and later, and CD
    10.0.4.0-ifix2 and later.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI82469

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-13

  • Closed date

    2022-04-05

  • Last modified date

    2022-04-05

  • 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

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]

Document Information

Modified date:
06 April 2022