[almighty] deploying SSL certs

[Max Rydahl Andersen]

nice! just tested and it works (with your described caveats).

have you created issues for the things that needs doing ?

/max

> Hi,
>
> On 09/09/16 10:51, Konrad Kleine wrote:
>> Hi Karanbir,
>>
>> that sounds like a plan. I'm totally for having something before
>> doing the real thing, if you know what I mean.
>>
>> Potentially we may run into issues and it would be nice if we can
>> eliminate them before doing the real thing.
>
> https://demo.almighty.io/ is now using a self hosted CA's generated
> SSL - so its not going to verify for the browser; will need accepting
> the first time you hit it.
>
> https://demo.api.almighty.io/ is now also online. Using a similar cert.
>
> Since the UI is hardwired to use http://demo.api.almighty.io/ the
> https port on api gets no traffic. Further compounding the problem is
> that most browsers will block secure/insecure mix. So visiting
> https://demo.almighty.io/ presently returns no content till that
> 'secure/insecure' content protection is turned off.
>
> all http:// traffic is still working as it was before. once we have
> these issues turned off, we can move to redirecting that to https as a
> default.
>
> regards,
>
> - --
> Karanbir Singh, Project Lead, The CentOS Project, London, UK
> Red Hat Ext. 8274455 | DID: 0044 207 009 4455
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>


/max
http://about.me/maxandersen