SAP Design Studio 1.5 - HTTPS OpenDocument URL into Embedded Frame

[AurelienVadiAgileDSS]

Hi folks !

I'm still workingi n SAP design studio 1.5 SP 2 (we plan to move to latest release in May) and I'm facing an issue.

Context :

• I need my applications to display in an embeddedframe a webi document through an opendocument call.
• I use SCN 2.0 embeddedframe component and buildopendocument URL in my application to set the embedded frame URL
• my sandbox environment is unsecured (HTTP) whilemy dev environnement is secured (HTTPS)
• my application is composed of 2 panels : one's got buttons to generates different opendocument URLs , the second has only an SCN embedded frame 2.0 in it

Issue :

• My sandbox works fine:
  1. I click on a specific button,
  2. It generates a correct URL http://biserver/opendocument/..
  3. It sets my embeddeframe URL to this URL
  4. My webi is loaded into my embeddedframe
  5. I still have access to my buttons, so I cangenerates otherurl and display other webi docs
• My developpement doesn’t work properly :
  1. I click on a specific button,
  2. It generates a correct URL https://biserver/opendocument/..
  3. It sets my embeddeframe URL to this URL
  4. My webi is loaded into my embeddedframe
  5. My embedded frame takes the whole application space, so I don’t have access to my buttons anymore

==> It seems that’s the only difference is theHTTPS in dev instead of http.

I saw into the component page that there aresome function on the domain relax level but no help is provided…

Does anybody know if I can fix my problem with such function and how it works ?

Is this a known issue that has been fixed in3.0 (for DS 1.6) ?

Any help would be appreciate,

Aurelien

[franckblais]

Hi Aurelien,

I fixed the domain relax on the embedded frame last time, but it was for another issue. I don't know well how it's working unfortunately ... Maybe Mike or Karol.

Btw, you should post it here instead: https://github.com/org-scn-design-studio-community/sdkpackage/issues This space is for demo applications.

See you next time :)

[entmike]

I've not performed any domain relaxation tactics in years (my BSP/iView hacking days) - I'd be too scared I'd just mess something else up. I'm not even sure I'd be able to get it to work with mixing https/http. Maybe Karol? :)

[MartinPankraz]

Hi guys,

Actually I implemented that domain coding so that you can get the iframe to work in relaxed domain scenarios where the root domain is common to both the container site and the called site on the iframe. All common browsers will prohibit security breaches though. Meaning you can't call an unsecure site from a secure one. If you check your browsers developer console you will see that error I am talking about. Usually issues like that are tackled by switching domains, makeing your unsecure site also secure (https) or put in a reverse proxy which reroutes your http calls so that the browser does not know about domain or http protocol breaches.

Let us know if we can be of any other help.

Regards Martin