Story #15211: Fixing deployment since separated certificates. #3526
+88
−85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GiooDev
added
bug
Collaborator
|
New Issues (1)Checkmarx found the following issues in this Pull Request
Fixed Issues (14)Great job! The following issues were fixed in this Pull Request
Use @Checkmarx to interact with Checkmarx PR Assistant. |
GiooDev
force-pushed
the
story_15211_quick_fix
branch
3 times, most recently
from
538c30b to
a3e384f
Compare
GiooDev
changed the title
GiooDev
force-pushed
the
story_15211_quick_fix
branch
from
a3e384f to
e442a9b
Compare
GiooDev
commented
Jan 31, 2026
| owner: "{{ vitamui_defaults.users.vitamui }}" | ||
| group: "{{ vitamui_defaults.users.group }}" | ||
| mode: "{{ vitamui_defaults.folder.conf_permission }}" | ||
| when: vitamui_struct.secure | default(secure) | bool |
Contributor
Author
There was a problem hiding this comment.
À revoir à l'occasion car ce n'est pas bon.
En effet, si on désactive le secure sur le composant en cours de déploiement, il peut avoir besoin du truststore_vitamui pour les appels suivants si les composants qu'il appelle sont configuré en https (secure: true).
GiooDev
force-pushed
the
story_15211_quick_fix
branch
from
e442a9b to
8b67888
Compare
GiooDev
commented
Jan 31, 2026
| trust-store-password: {{ password_truststore }} | ||
| trust-store: {{ vitamui_folder_conf }}/truststore_vitamui.jks | ||
| trust-store-password: {{ truststores_vitamui }} | ||
| client-auth: want |
Contributor
Author
There was a problem hiding this comment.
On pourrait configurer en client-auth: need puisque tous les appels effectués à iam semblent être fait en mTLS.
Contributor
Author
|
Toujours une erreur |
GiooDev
force-pushed
the
story_15211_quick_fix
branch
2 times, most recently
from
60e7f0c to
8725335
Compare
GiooDev
force-pushed
the
story_15211_quick_fix
branch
2 times, most recently
from
57bd26e to
7e3ff4d
Compare
GiooDev
force-pushed
the
story_15211_quick_fix
branch
from
7e3ff4d to
6211bc3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Ansible
Architecture
Here is the current network architecture:
graph TD %% Service Definitions RP[Reverse Proxy] subgraph SERVICES_UI[VitamUI-UI Services] direction TB UPO[ui-portal] UID[ui-identity] UIA[ui-identity-admin] UAS[ui-archive-search] URE[ui-referential] UCO[ui-collect] UPA[ui-pastis] UIN[ui-ingest] end API_GW[api-gateway] CAS[cas-server] subgraph VITAM_UI_SERVICES[VitamUI Services] direction TB subgraph VUI_SERVICES[ ] direction TB R[referential] P[pastis] I[ingest] C[collect] AS[archive_search] end IAM[iam] SEC[security] end %% Communications EXTERNAL -->|https| RP RP -->|http| SERVICES_UI RP -->|https| CAS SERVICES_UI -->|mTLS| API_GW API_GW -->|https + x-ssl-cert| VITAM_UI_SERVICES VUI_SERVICES -->|mTLS| IAM VUI_SERVICES -->|https| SEC IAM <-->|mTLS| CAS IAM -->|https| SECType de changement
Contributeur