Skip to Content
author's profile photo Former Member
Former Member

Digital Signature Expiration

We are currently running 5.1 SP6 and are a little confussed with all the release notes that have been posted regarding the digital signature expiration as to whether or not our version will be affected by this. From the most current release notes, it sounds like versions BPC 7M SP3, BPC 5.1 SP7, BPC 5.1 SP8, and CPM 4.2 SP05 Patch 1 are the only ones that will be affected. Is this true?

It also sounds like it is more of a nusance than anything because you will recieve a warrning message if your security level is set to very high so you would have to change your security to a lower level. It doesn't sound like any system funcationality will be affected. Is this also true?

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 23, 2009 at 02:13 PM

    Hi,

    yes these versions are only affected by this other versions are fine.

    Yes this is related to security warning only and you just need to decrease the security level for this. this will not affect any functionality of BPC.

    regards,

    sreedhar

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      according to the SAP development only the versions mentioned above will be affected others are fine. So you need to consider when your build is listed there otherwise you can ignore it. I am not sure if there will be any place to look into to find the build numbers.

      regards,

      Sreedhar

  • author's profile photo Former Member
    Former Member
    Posted on Aug 04, 2009 at 10:23 PM

    Guess I a little confused (what is new). The digital Signature is associated with the EV4Process.xla file. So if we are on a release other than those indicated in the note(for example 4.2 sp4) and use this file (which is what I don't understand), then we will experience the expiration issue on the certificate. So I guess our question would be is the file/add-in Ev4Process.xla used in CPM 4.2 SP4?

    Thanks in advance.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 11, 2009 at 07:47 PM

    The digital signatures are for our excel components (add-ins). They must be signed (by verisign for example) in order for excel to allow them to run. The certificates expire, really they are not supposed to but there was a glitch in the these particular builds that allows them to expire, once they expire it could render BPC for Office unusable. This depends on Office's macro security, for example, if in excel your macro security is set to High, when you run BPC you will get a message that says the macros are unsigned and won't them be invoked. If you macro security is set to medium you will only get a warning and it will let BPC load if you click Ok on the warning.

    These are the only versions that are effected.

    Links to SAP notes with more information on the patch and to download the patch:

    4.2 SP5 - https://service.sap.com/sap/support/notes/1334222

    5.1 SP7 - https://service.sap.com/sap/support/notes/1334157

    5.1 SP8 - https://service.sap.com/sap/support/notes/1334216

    7.0 SP3 - https://service.sap.com/sap/support/notes/1334217

    Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.