IBM Support

IT19167: DATA IS TRUNCATED AFTER COLON SIGN WHEN USED IN CUSTOMPROTOCOLEXTENTION FIELD

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

  • Using the REST API to create trading partner in IBM Sterling B2B
    Integrator V5.2.6.2 and using Custom Protocol Extensions,
    we can see that if the data such as a fingerprint key contains
    the Colon sign (used as
    separator of values in that field).
    This results in truncation of the data after the colon sign once
    updated in the database.
    Since the data is passed as a string to the database,
    no substitution character works to make the field have a
    correct and expected value in database.
    
    In REST API format standard, the Colon sign must not be used in
    member names but their is no specification or restriction for
    the data.
    

Local fix

  • RTC - 527475
    EJ / EJ
    No workaround
    

Problem summary

  • Users Affected:
    All users who uses trading partner API.
    
    Problem Description:
    Using the REST API to create trading partner in IBM Sterling B2B
    Integrator V5.2.6.2 and using Custom Protocol Extensions,
    we can see that if the data such as a fingerprint key contains
    the Colon sign (used as
    separator of values in that field).
    This results in truncation of the data after the colon sign once
    updated in the database.
    Since the data is passed as a string to the database,
    no substitution character works to make the field have a
    correct and expected value in database.
    
    In REST API format standard, the Colon sign must not be used in
    member names but their is no specification or restriction for
    the data.
    
    
    Example of value used for the customprotocolextention field :
    "customProtocolExtensions":
    "PGP_C_ENCRYPT:no,SFTPSCPENABLED:TRUE,ENCRYPTIONMETHOD:PGPPK,FG
    CUST-SFTPPUT_ProfileId:sv144729:node1:158d2fc5dfa:171,DMIROUTE
    ILLCONSUME:TRUE,CONSUMERCONNECTION:LISTENCONNECTION,PROTOCOLBPN
    ME:FG-CUST-SFTPPUT,DMIROUTECONSUMERIDPOLICY:FILEGATEWAY,DMIROUT
    _WILLPRODUCE:TRUE,FG-CUST-SFTPPUT_HostFingerPrint_sftp:ssh-rsa
    1024
    cb:79:be:bc:83:f4:fd:97:2e:4d:30:47:f5:1c:95:76,DMIROUTECONSUME
    PROTOCOLPOLICY:MAILBOX,PGP_C_COMP:no,PGP_P_ENCRYPT:no,AUTHORIZE
    USERKEYENABLED:TRUE,PGP_C_SIGN:no,TEXTMODE:off,ASCIIARMOR:off",
    
    This example will result in the database to the following value:
    
    
    FG-CUST-SFTPPUT_HostFingerPrint_sftp = sftp:ssh-rsa 1024 cb
    instead of ssh-rsa 1024
    cb:79:be:bc:83:f4:fd:97:2e:4d:30:47:f5:1c:95:76
    
    CUST-SFTPPUT_ProfileId = sv144729 instead of
    sv144729:node1:158d2fc5dfa:171
    
    
    Platform Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    
    
    
    Delivered In:
    5020602_4
    5020603_2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19167

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-08

  • Closed date

    2017-05-13

  • Last modified date

    2017-06-19

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R526 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
19 June 2017