I started an instance of hello-openshift: https://hello-openshift-stage.1ec1.dev-preview-int.openshiftapps.com/ The router appears to use self-signed certs by default though, which not only causes annoying warnings for human web browser users, it precludes https:// use by automated services (e.g. github webhooks).
You will need to set up your keys on your routes: https://docs.openshift.com/enterprise/3.1/dev_guide/routes.html Or set up a wildcard cert for the default routing subdomain: https://docs.openshift.com/enterprise/3.1/install_config/install/deploy_router.html#using-wildcard-certificates
I'm aware I could bring my own keys, but I'd expect Online v3 to offer this by default. OpenShift v2 currently uses a wildcard *.rhcloud.com certificate from Digicert. Right?
Oh! Online... sorry, completely missed that part. Apologies. Yeah, I assume they will issue a cert. I'll reopen this.
Reassigning to Abhishek because this needs to be dispatched to whomever will get the Online SSL wildcard cert (if SSL will even be supported).
Tested SSL certs using utility below: https://www.digicert.com/help/?host=test.1ec1.dev-preview-int.openshiftapps.com https://www.digicert.com/help/?host=test.b795.dev-preview-stg.openshiftapps.com https://www.digicert.com/help/?host=test.44fs.preview.openshiftapps.com INT/STG/Prod pass.
Moving to ON_QA based on comment above by Stefanie.
QE verified this bug on INT/STG.