cancel
Showing results for 
Search instead for 
Did you mean: 

EmbedSecret property is not configured in the system: <alais> SAP_BO

former_member261631
Participant
0 Kudos

Hi,

We are having SAP Portal version 7.01 and use SAP BO 4.0 SPS005 to run SAP BO reports.

And recently we have upgraded SAP BO SPS version from SPS004 to SPS005. But due to the latest SPS005 version of SAP BO system, the SAP Portal does not able to publish SAP BO reports. As getting mention exception, while executing the report in SAP Portal:

Warning! The EmbedSecret property is not configured in the system with alias: SAP_BO. (FWC00009)

Inputs required to overcome this message from SAP Portal to properly run SAP BO reports.

Regards,

Hanif

Accepted Solutions (1)

Accepted Solutions (1)

former_member83199
Discoverer
0 Kudos

The error message you gave is telling you that you either have not given a value for the Embed Secret property or that property is not available on your Portal System Object SAP_BO.  You need to set the value of that property to the same value that is set in your BOE custom/global.properties file on BI4.0 system.

Make sure that the Enterprise Portal has the latest System Object and iView templates by applying to the Portal the EPA and PAR files from the BI4.0 system located in directory enterprise_xi40/warfiles/portlet/iviews.  If you don't have the latest EPA and PAR, the Embed Secret property may not be available on the Portal System Object.

com.sap.businessobjects.iviews.par

com.sap.businessobjects.iviews.templates.epa

We also ran into issues after we upgraded to BI4.0 due to new parameters introduced by the upgrade that were missing from our custom properties files.  After we compared the properties files from the default and custom subdirectories of enterprise_xi40/warfiles/webapps/BOE/WEB-INF/config/, we noticed new entries in the default directory files that were not present in the custom directory files.  Below is a summary of the properties files differences.  Note: I have not included our custom values.

enterprise_xi40/warfiles/webapps/BOE/WEB-INF/config/custom/BIlaunchpad.properties

Missing:

# The maximum number of elements in the object browser folder tree

max.tree.children.threshold=200

# History page refresh interval

# The history page refresh time in milliseconds.   This is applied when there are pending/running docs. It is

# consumed by the URE HistoryPanel reusable component.

# Scope: global

historypage.refresh.secmillis=10000

# Embed secret (enter your own)

# A shared secret between a portal embedding BOE applications and the BOE application server which is used to

# determine whether BOE applications can be safely embedded in other pages.

# Make sure you change in both places.

logon.embed.secret=

# Embed timeout

# Number of seconds after which BOE applications like BI Launchpad will reject being

# embedded into a portal. Make sure the system clocks on the BOE web server and portal server machines

# are within this number of seconds of each other.

logon.embed.timeout=300

enterprise_xi40/warfiles/webapps/BOE/WEB-INF/config/custom/BIlaunchpad.properties

No longer in default:

# Set to true to enable frame breaking on the login page to prevent Cross site framing security vulnerability.  Defaults to false if this is not present

enforceTopLevelFrame.enabled=false

Missing:

# whether to allow other pages to embed this application (as a frame) without passing a valid embed token.

logon.allowInsecureEmbedding=false

enterprise_xi40/warfiles/webapps/BOE/WEB-INF/config/custom/OpenDocument.properites

Missing:

# whether to allow other pages to embed this application (as a frame) without passing a valid embed token.

logon.allowInsecureEmbedding=false

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Hanif,

You can  resolve this issue by enabling following property  in BO side in
the file #openDocument.properties#, it  allow user to login directly from portal without any error message. Added file to custom folder and edit this property.

# whether to allow other pages to embed this application (as a frame)
without passing a valid embed token.
logon.allowInsecureEmbedding=true


Regards

Shrikant

former_member261631
Participant
0 Kudos

Hi Shrikant,

Thanks for the reply..

In SAP BO intsllation drive we checked in the file openDocument.properties: the embed property value is already set to true

logon.allowInsecureEmbedding=true

The reports are running fine, but initially this message pops-up with logon to document page for a second and afterwards SAP BO reports get executed in SAP Portal properly.

Any other property to check?

Regards,

Hanif

former_member220449
Participant
0 Kudos

Hello Hanif.

We have the same issue as well.

I doubt if the problem is about logon.embed.secret parameter in the global.properties file.

The description of the parameter is as:

# Embed secret (enter your own)

# A shared secret between a portal embedding BOE applications and the BOE application server which is used to

# determine whether BOE applications can be safely embedded in other pages.

# Make sure you change in both places.

Former Member
0 Kudos

Hello,

Secure embedding may be achieved by following the steps mentioned in the following KB:1804310

Whereby the "Embed Secret" is field in the "SAP Businessobjects" Property category of the BI4 SP5 System landscape is populated with a string which would match what is in BI4 global.properties.

(

a) Stop Tomcat

b) Go to C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF\config\default\global.properties file

c) Add  property logon.embed.secret=secret  (same as given in the SAP Enterprise Portal).

d) Restart Tomcat")

thanks,

Akin