You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/documentation/architecture.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Architecture Overview
26
26
For more details on generic integration components (webservices, I/O interface, etc.) please refer to the documents referenced in the _Integration services_ section of [the documentation index](/docs/documentation/integration/in-out).
27
27
Some of these generic webservices are wrapped into generic libraries/APIs in various technologies, please refer to the documents referenced in the _APIs_ section of the document index.
28
28
29
-
Beyond these generic integration components, Simplicité being a Java platform, any kind of integration that is possible in Java is possible with Simplicité.
29
+
Beyond these generic integration components, Simplicité being a Java platform, any kind of integration that is possible in Java is possible with Simplicité.
30
30
Some examples are available in [this document](/docs/documentation/core/third-party-apis-examples) but many other third part public or private services integration can be implemented.
31
31
32
32
Compliance
@@ -60,6 +60,6 @@ In this mode the publication layers (UI and API) have access to an EJB wrapped S
60
60
Clustering
61
61
----------
62
62
63
-
Simplicité instances can be clustered to provide several nodes using the same database, the right approach for load balancing being a **sticky session** load balancing.
63
+
Simplicité instances can be clustered to provide several nodes using the same database, the right approach for load balancing being a **sticky session** load balancing.
When using an Apache or NGINX webserver as reverse proxy you can configure it to enforce client certificate authentication (see [this document](/docs/documentation/misc/webserver-ssl) for details).
53
53
54
54
They typically can be configured to propagate the verified client certificate's DN as the `X-SSL-Client-S-DN` HTTP header.
55
-
Then the authentication on Simplicité side is easy as it is just a matter of parsing this DN, e.g. extracting the `CN` field as login:
55
+
Then the authentication on Simplicité side is easy as it is just a matter of parsing this DN, e.g. extracting the `CN` field as login:
Copy file name to clipboardExpand all lines: docs/documentation/compatibility.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This document gives a non exhaustive list of architectures and infrastructure co
11
11
Containers deployments (Docker and PaaS)
12
12
----------------------------------------
13
13
14
-
The **ideal** / **preferred** deployment model is to deploy Simplicité platform as **Docker® container(s)**
14
+
The **ideal** / **preferred** deployment model is to deploy Simplicité platform as **Docker® container(s)**
15
15
from our standard pre-built images available on [DockerHub](https://hub.docker.com/r/simplicite/) or from custom images that you build to fit your needs.
16
16
See [this document](/docs/documentation/operation/docker) for details.
17
17
@@ -24,20 +24,20 @@ It is also possible to deploy it as managed application container(s) on a wide r
24
24
Etc.
25
25
26
26
In both cases you will need an external database service - custom or as a service (DBaaS).
27
-
See the "Databases" section for details on Simplicité database compliances.
27
+
See the "Databases" section for details on Simplicité database compliances.
28
28
29
29
Custom deployments
30
30
------------------
31
31
32
-
It is still possible, although highly **discouraged**, to deploy Simplicité on custom IaaS infrastructures or even on premises servers.
32
+
It is still possible, although highly **discouraged**, to deploy Simplicité on custom IaaS infrastructures or even on premises servers.
33
33
In such a case you need to verify that your technical platform complies with the following recommendations.
34
34
35
35
### Introduction
36
36
37
37
By default, our **recommendation** is that you use only the current **up to date** versions of **all technical components**
0 commit comments