Difference between revisions of "SOA3 Development Plan"
(Created page with 'This page contains a series of steps suggested in order to deploy gCube Secure infrastructure: 0. Start the integration of standalone clients with common-security library (look …') |
|||
| Line 4: | Line 4: | ||
1. Define a reference CA with a certificate, and a revocation list | 1. Define a reference CA with a certificate, and a revocation list | ||
| + | |||
2. Define and host certificate for every Node | 2. Define and host certificate for every Node | ||
| + | |||
3. Deploy the secure container and disable security | 3. Deploy the secure container and disable security | ||
| + | |||
4. Start the core services enabling TLS and enable client security for all the Nodes (look at [[GCube Security Configuration]]) and reconfigure the endpoints of the core services with HTTPS | 4. Start the core services enabling TLS and enable client security for all the Nodes (look at [[GCube Security Configuration]]) and reconfigure the endpoints of the core services with HTTPS | ||
| + | |||
5. first session of integration tests | 5. first session of integration tests | ||
| + | |||
6. enable message level security for the services whose clients have been successfilly modified (look at [[GCube Security Configuration]]) | 6. enable message level security for the services whose clients have been successfilly modified (look at [[GCube Security Configuration]]) | ||
| + | |||
7. proceed progressively till the integration and tests of all the services and clients | 7. proceed progressively till the integration and tests of all the services and clients | ||
| + | |||
8. remove any per service configuration (if not explicitely needed) and use default server security configuration | 8. remove any per service configuration (if not explicitely needed) and use default server security configuration | ||
| + | |||
9. authentication totally enabled and working | 9. authentication totally enabled and working | ||
Revision as of 11:23, 11 March 2013
This page contains a series of steps suggested in order to deploy gCube Secure infrastructure:
0. Start the integration of standalone clients with common-security library (look at GCube Clients Integration with security)
1. Define a reference CA with a certificate, and a revocation list
2. Define and host certificate for every Node
3. Deploy the secure container and disable security
4. Start the core services enabling TLS and enable client security for all the Nodes (look at GCube Security Configuration) and reconfigure the endpoints of the core services with HTTPS
5. first session of integration tests
6. enable message level security for the services whose clients have been successfilly modified (look at GCube Security Configuration)
7. proceed progressively till the integration and tests of all the services and clients
8. remove any per service configuration (if not explicitely needed) and use default server security configuration
9. authentication totally enabled and working
