Refactor to use provided C2C TLS encryption

[davemcorwin]

Story

In order to simplify the application and leverage the platform, Pages Operators want to remove the https configuration and use the platform provided C2C TLS encryption.

Acceptance Criteria

GIVEN running on cloud.gov

• WHEN a client attempts to access the server at the default port with https THEN it should fail
• WHEN a client attempts to access the server at port 61443 with https THEN it should succeed
• WHEN a client attempts to access the server at default port or 61443 with http THEN it should fail

GIVEN running locally

• WHEN a client attempts to access the server at the default port with http THEN it should succeed
• WHEN a client attempts to access the server at default port or 61443 with https THEN it should fail

---

Security considerations

Leverages cloud.gov provided C2C TLS encryption, allowing clients to access over port 61443 without having to ignore cert errors.

Implementation sketch

• Remove the https configuration
  • config definition
  • config export
  • config import
  • config usage

Post deployment

• Modify clients (federalist web) to use https on port 61443 and remove any allowance for certificate errors.