TBD. This is the first agreed upon use case for the examples listed below which is to focus on creating and exposing endpoint configuration information.

Examples:
a) OS admin access - Cloud may provide key pair. For clouds that don't provide SSH key pairs, install SSH keys (or accept password security).
b) MySQL admin - Create optional separate SSH account or use OS SSH, Configure DB admin password
c) Application via SSL - Install specific SSL certs on WebServer Tier or Load Balancer
d) Application clear and SSL - May need to configure VirtualHosts (or like concept)

Notes:
Matt: There seems to be multiple scenarios for this page of the presentation. Do any need a separate issue? Can all or some be represented using a single use case? It seems there are pre-deploy (provide keys), during deploy (access to keys) and post deploy considerations (keys, IPs, access information).
Derek: would break it down into endpoint config (exposing, creating). Should be a pattern that can be used over and over. Other case is admin access. to comp endpt. for admin purposes (consoles).
Matt: 2 use cases need to be opened

References:
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48513/TOSCASugarCRMUseCase-CompleteConnectivity.pptx
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48514/ConsiderationsFor2TierWebApplications.docx