IBM Support

IC98766: SWIFT ERROR MESSAGE "SECURITY CONTEXT HAS BECOME INVALID" HAS NO AUTOMATIC RECOVERY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Currently no automatic action is taken when SWIFT
    replies with the error "security context has become invalid."
    
    The SWIFT response looks like this:
    <SwGbl:StatusAttributes>
                <SwGbl:Severity>Logic</SwGbl:Severity>
                <SwGbl:Code>Sw.Gbl.HSMContextLost</SwGbl:Code>
                <SwGbl:Parameter>DN for the security
    context</SwGbl:Parameter>
                <SwGbl:Parameter>SessionId=sessionId
    :LocalError=-100065 :FuncID=125 :EntrustError=0 [HSM token not
    present.] [HSM token not present.]  [] </SwGbl:Parameter>
                <SwGbl:Text>Security context has become
    invalid.</SwGbl:Text>
                <SwGbl:Details>
                    <SwGbl:Code>Sw.Sec.HSMContextLost</SwGbl:Code>
                    <SwGbl:Text>Security context has become
    invalid., DN=DN entry, SessionId=sessionId :LocalError=-100065
    :FuncID=125 :EntrustError=0 [HSM token not present.] [HSM token
    not present.]  [] </SwGbl:Text>
                    <SwGbl:Action>Reestablish the session for this
    DN by performing DestroyContext and followed by
    CreateContext.</SwGbl:Action>
                </SwGbl:Details>
            </SwGbl:StatusAttributes>
            <SwGbl:StatusAttributes>
                <SwGbl:Severity>Logic</SwGbl:Severity>
                <SwGbl:Code>Sw.Gbl.HSMContextLost</SwGbl:Code>
    <SwGbl:Parameter>DN=dnID</SwGbl:Parameter>
                <SwGbl:Parameter>Level=1</SwGbl:Parameter>
                <SwGbl:Parameter>SessionId=sessionId
    :LocalError=-100065 :FuncID=125 :EntrustError=0 [HSM token not
    present.] [HSM token not present.]  [] </SwGbl:Parameter>
                <SwGbl:Text>Security context has become
    invalid.</SwGbl:Text>
            </SwGbl:StatusAttributes>
    
    Recommmented action from SWIFT:"Reestablish the session for
    this DN by performing DestroyContext and followed by
    CreateContext."
    
    Without any further action all transfer to this DN and all DN
    which use the same security context will fail.
    

Local fix

  • STRRTC - 406713
    SKorn / SKorn
    
    Circumvention:
    Restart of the SWIFTNet7 adapter.
    During restart of the adapter the security context will be
    destroyed and a new context will be created.
    

Problem summary

  • SWIFTNet7 adapter ia not able to auto-recover when receiving
    the error "Security Context has become invalid." You must stop
    and restart the adapter.
    
    User Affected:
    SWIFTNet7 adapter users
    
    Platform Affected:
    All
    

Problem conclusion

  • A code fix has been applied.
    
    Delivered In:
    5020500_4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC98766

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    523

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-16

  • Closed date

    2015-03-03

  • Last modified date

    2015-04-27

  • 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

  • R525 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.3","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
27 April 2015