This repository has been archived by the owner on Feb 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
FAQ
Thanos edited this page Nov 18, 2019
·
8 revisions
This page is an ongoing effort to capture the most frequently asked questions regarding installing and operating the MeliCERTes CSP framework.
| What are the hardware requirements for installing CSP local node? |
|---|
| The minimum hardware requirements are 4 x CPU Intel® Xeon® CPU E5-2695 v2 @ 2.40Ghz, 24 GB RAM, 128 GB SSD. |
| What software do I need? |
|---|
| You can download the initial VM in OVA format from the ENISA portal which needs the following software: - Hypervisor: VMWare ESXi (free1) or variant, v6.5 or above. - Windows machine with VSphere / VCenter software to facilitate the import of the virtual machine to the ESXi server. |
| How do I build the software? |
|---|
| You do not need to build the software as you can download the initial VM in OVA format. However, if you still want to build the software from the code than follow the instructions in CSP_BUILD_INSTRUCTIONS. |
| Why do we need Windows and ESXi? |
|---|
| The CSP local node is a single VM that can be deployed in any hypervisor such as KVM, ProxMox, ESXi, and Hyper-V. The platform has been tested with ESXi which is why it is recommended. |
| What ports need to be open? |
|---|
| To install and operate CSP requires access to the internet, both outbound and inbound. See the Installation Manual for the exact port numbers. |
| How do I know if my local CSP node is correctly installed? |
|---|
| See "Check if CSP local node is correctly installed" in the "How To..." section for detailed instructions to check if your local CSP node correctly installed and operational. |
| What characters are allowed to create user accounts? |
|---|
| CSP uses ForgeRock OpenAM for access management. See the OpenAM specifications for how to use this module (https://github.com/ForgeRock/openam-community-edition). |
| Why is my authentication module missing in OpenAM/Realms/Authentication/Modules? |
|---|
1. Enter the Docker container: docker exe -ti csp-oam /bin/bash
|
2. Change directory to the /opt/ssoadm cd /opt/ssoadm
|
3. Run the post installation script: ./post-config-openam.sh
|
4. After a few minutes you should see: ! Post configuration complete!
|
5. Exit the container: exit
|
6. Restart csp-oam and csp-apache: docker restart csp-oam docker restart csp-apache
|
| 7. The CSP-Certs should now be listed on the OpenAM Administration Page in your browser |
| Why it the Jitsi admin not sending out emails? |
|---|
By default TLS is configured and if your mail server is using SSL then emails will get blocked. Update the configuration in /opt/csp/modules/vcb/docker-compose.yml:command sh -c "sleep 10 && java -Xmx512m -Dspring.profiles.active=docker -Dspring.mail.properties.mail.smtp.starttls.enable=true -Dspring.mail.properties.mail.debug=true -Dlogging.level.com=DEBUG -jar server.jar Run the docker command: docker-compose up -d |
For more detailed troubleshooting check the Mail troubleshooting page
| Why is MISP not working after updating other modules? |
|---|
| It is possible that updating another module in CSP may affect the MISP installation. See the Docker Cheat Sheet on how to fix this. |