Changes for page Paramètres des URL pour l'intégration Web

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-xwiki:XWiki.aureliebertranddigdashbiz
	1	+xwiki:XWiki.jhurst

Content

...	...	@@ -5,19 +5,26 @@
5	5
6	6	DigDash can be embedded at multiple “levels” in external websites:
7	7
8		-* Dashboard
9		-* Dashboard page
10		-* Information {{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}}
	8	+-Dashboard
11	11
	10	+-Dashboard page
	11	+
	12	+-Information Flow
	13	+
12	12	In this document we will present url that works in the following context:
13	13
14		-* Server name: ddsrv
15		-* Port: 8080
16		-* DigDash Domain: ddenterpriseapi
17		-* DigDash Dashboard Domain: digdash_dashboard
	16	+Server name: ddsrv
18	18
	18	+Port: 8080
	19	+
	20	+DigDash Domain: ddenterpriseapi
	21	+
	22	+DigDash Dashboard Domain: digdash_dashboard
	23	+
	24	+
19	19	= Dashboard =
20	20
	27	+
21	21	At this level you can embed multiple pages in an iframe.
22	22
23	23	URL : http:~/~/ddsrv:8080/digdash_dashboard/index.html
...	...	@@ -80,8 +80,10 @@
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}} =
84	84
	91	+= Information Flow =
	92	+
	93	+
85	85	At this level you can embed one information flow (graphic component) of your information wallet into an iframe
86	86
87	87	URL: http:~/~/ddsrv:8080/ddenterpriseapi/viewflow?flowId=<flowid>
...	...	@@ -129,19 +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 =
133	133
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
136		-The solution is to use an attribute //SameSite=None// on the cookie. This attribute must be set be the application container (Tomcat), or the HTTP front server (eg. Apache httpd). There are various available documents online to configure this cookie attribute. For tomcat's cookies : [[https:~~/~~/tomcat.apache.org/tomcat-9.0-doc/config/cookie-processor.html>>https://tomcat.apache.org/tomcat-9.0-doc/config/cookie-processor.html]]. On the Apache httpd side, the use of mod_headers module may be required.
137	137
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		-
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		-
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]]
143		-
144		-
145		-
146		-
147	147