Commit 61f1b733e82e20ce031fcde078f64a2ebdac8368
1 parent
208ac9d6
Exists in
master
and in
3 other branches
Very tiny changes on architecture
Showing
1 changed file
with
7 additions
and
7 deletions
Show diff stats
opensym2017/content/05-architecture.tex
... | ... | @@ -39,10 +39,10 @@ described how we integrated those tools and conclude with the deployment. |
39 | 39 | |
40 | 40 | \subsection{Colab} |
41 | 41 | |
42 | -Colab\footnote{\url{https://github.com/colab/colab}} has integration of web | |
43 | -applications as its main goal, the user of this integrated system should not | |
44 | -notice the change between the integrated applications. To do that Colab was | |
45 | -designed to use plugins of each application and has four levels of integration: | |
42 | +Colab integrates web applications as its main goal, the user of this composed | |
43 | +system should not notice the change between the integrated applications. Colab | |
44 | +was designed to use one plugin for each system under its domain, this is | |
45 | +guaranteed by four levels of integration: | |
46 | 46 | |
47 | 47 | \begin{itemize} |
48 | 48 | \item Authentication |
... | ... | @@ -51,13 +51,13 @@ designed to use plugins of each application and has four levels of integration: |
51 | 51 | \item Data and search engine |
52 | 52 | \end{itemize} |
53 | 53 | |
54 | -Colab works as a reverse proxy, therefore all external requests pass through | |
55 | -it, this is an advantage to manage these four levels of integration. | |
54 | +The aforementioned integrations levels were possible, because Colab works as a | |
55 | +reverse proxy, therefore all external requests pass through it. | |
56 | 56 | |
57 | 57 | Single Sign-On (SSO) is used to login users throughout all integrated |
58 | 58 | applications. REMOTE\_USER HTTP header is sent to the applications and we |
59 | 59 | expect that they know how to handle it, since this is a common authentication |
60 | -mechanism. The integrated applications should be in a local network to avoid | |
60 | +mechanism. The integrated applications should be on a local network to avoid | |
61 | 61 | security issues. With this the user will be able to navigate through the |
62 | 62 | platform applications and will not be asked for authentication credentials. |
63 | 63 | ... | ... |