Symantec IGA

 View Only
  • 1.  FIPSKey Path Error

    Posted Aug 08, 2018 01:33 AM


    We are seeing the below error more frequently in IM logs.


    DEBUG [com.netegrity.crypto.AESCBCPKCS5PaddingHandler] (default task-54) ************The key path =/com/netegrity/config/keys/FIPSkey.dat
    ERROR [com.netegrity.crypto.AESCBCPKCS5PaddingHandler] (default task-54) Exception caught while decrypting.
    ERROR [com.netegrity.crypto.AESCBCPKCS5PaddingHandler] (default task-54) org.bouncycastle.util.encoders.DecoderException: unable to decode base64 data: invalid characters encountered in base64 data


    Is this product default behaviour to search for FIPS key under above specified path ?

  • 2.  Re: FIPSKey Path Error
    Best Answer

    Broadcom Employee
    Posted Aug 08, 2018 08:21 AM

    Hi Sriram,


    The key path is correct because the key file is found.

    When it is not found you get a specific error message.

    For me this is not possible to determine the root cause of this issue.
    Opening a ticket with CA Support will be a better approach.
    Giving the exact context; Software or Virtual appliance implementation, Release version, Service Pack, Cumulative Patch, Hot Fixes, Installation from scratch or upgrade,
    happening in a start up step or when doing specifics tasks once IME is up, etc.




  • 3.  Re: FIPSKey Path Error

    Posted Aug 09, 2018 08:05 AM

    Thank you Philippe. Will open a case with CA.