Last modified by Aurelie Bertrand on 2025/02/07 10:22

From version 4.1
edited by Aurelie Bertrand
on 2025/02/07 10:22
Change comment: Copied from dev:Digdash.customization.url_parametres.WebHome
To version 2.1
edited by fperrier
on 2022/03/14 17:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.aureliebertranddigdashbiz
1 +xwiki:XWiki.fperrier
Content
... ... @@ -7,7 +7,7 @@
7 7  
8 8  * Dashboard
9 9  * Dashboard page
10 -* Information {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}}
10 +* Information Flow
11 11  
12 12  In this document we will present url that works in the following context:
13 13  
... ... @@ -80,7 +80,7 @@
80 80  [[http:~~/~~/ddsrv:8080/digdash_dashboard/index.html?page=user1.page1&domain=ddenterpriseapi&login=user1&pass=pass1&hideBanner=true&hideFilters=true&var=1>>url:http://ddsrv:8080/digdash_dashboard/index.html?page=user1.page1&domain=ddenterpriseapi&login=user1&pass=pass1&hideBanner=true&hideFilters=true&var=1]]
81 81  )))
82 82  
83 -= Information {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} =
83 += Information Flow =
84 84  
85 85  At this level you can embed one information flow (graphic component) of your information wallet into an iframe
86 86  
... ... @@ -129,7 +129,7 @@
129 129  http:~/~/ddsrv:8080/ddenterpriseapi/viewflow?flowId=2340fd0&user=user1&pass=pass1&Geo=France&HGeo=Geography&LGeo=Country
130 130  )))
131 131  
132 -= Security Constraints =
132 += Security Considerations =
133 133  
134 134  Some browsers, for example Chrome from its version 80, may refuse to process cookies that are coming from embedded webpages if the iframe site host is different than the embedding page.
135 135  
... ... @@ -137,11 +137,13 @@
137 137  
138 138  However, the attribute //SameSite //can not be set on an non-secure cookie. So the //Secure //attribute must be set as well to be able to set SameSite=None. And the //Secure //attribute must be set only for HTTPS site.
139 139  
140 -So, consequently, embedding a DigDash Enterprise dashboard, or viewflow page, in an iframe,** if the embedding page and the iframe have different hosts**, will require to use an HTTPS connexion, and to configure cookie processing.
140 +So, consequently, embedding a DigDash Enterprise dashboard, or viewflow page, in an iframe,** if the embedding page and the iframe have different hosts**, will require to use an HTTPS connexion, and to configure cookie processing.
141 141  
142 -The following Mozilla document this requirements : [[https:~~/~~/developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite>>url:https://developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite]]
142 +The following Mozilla document this requirements :
143 143  
144 +[[https:~~/~~/developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite>>url:https://developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite]]
144 144  
145 145  
146 146  
148 +
147 147