In 2018 Khoros is moving all customer sites to SSL encryption (HTTPS) to safeguard customer data. HTTPS encrypts all data passed between the end user and your community. Khoros is ready to work with you to enable, test, and deploy a SSL certificate, to bring your community to full HTTPS delivery. We will also be sending out email notifications to our customers over the next month and a half as a reminder on this.
These changes will result in:
Note that the steps below follow Khoros Standard SSL deployment. Access to Standard SSL deployment is included with existing customer licenses (is free).
To get started, we ask that you follow the following steps.
Why is Khoros switching to HTTPS now?
Major browser and search vendors are making changes to flag pages that are delivered over HTTP as 'not secure' after July 2018. Obviously, this kind of message is not one you want associated with your brand. HTTPS is also a factor in search engine ranking. It's presumed that search vendors will add additional weight to HTTPS in their ranking formula this year.
What if part of my community is delivered over HTTPS already?
For customers using "mixed mode", Khoros will work with you to enable full site HTTPS using the existing SSL certificate. The steps required on your part are identical for customers using mixed mode.
Can I wait?
Not for much longer. Khoros is phasing out support for HTTP communities after 18.7, following best practices and maintaining our commitment to securing customer data.
Can I generate my own certificate?
Contact support or your account team for alternative SSL certificate scenarios. Note that alternative scenarios generally carry a charge and require an engagement (SOW). We typically advise against this direction.
What about external domains?
Anything hosted on the community will support HTTPS. However, any references to external domains will require that those domains be under SSL. If you’re using an external asset and the domain does not support HTTPS, we recommend that you upload the asset to your community via studio then update the reference code/URL.
What is a SAN SSL certificate?
See the What is the SAN SSL certificate? Article.
What are the benefits of using SSL (HTTPS encryption)?
See the Full HTTPS Encryption for all Communities article.
Thank you for your time and we look forward to working with you to migrate you to HTTPS!
In 2018 Khoros is moving all customer sites to SSL encryption (HTTPS) to safeguard customer data. HTTPS encrypts all data passed between the end user and your community. Khoros is ready to work with you to enable, test, and deploy a SSL certificate, to bring your community to full HTTPS delivery. We will also be sending out email notifications to our customers over the next month and a half as a reminder on this.
These changes will result in:
Note that the steps below follow Khoros Standard SSL deployment. Access to Standard SSL deployment is included with existing customer licenses (is free).
To get started, we ask that you follow the following steps.
Why is Khoros switching to HTTPS now?
Major browser and search vendors are making changes to flag pages that are delivered over HTTP as 'not secure' after July 2018. Obviously, this kind of message is not one you want associated with your brand. HTTPS is also a factor in search engine ranking. It's presumed that search vendors will add additional weight to HTTPS in their ranking formula this year.
What if part of my community is delivered over HTTPS already?
For customers using "mixed mode", Khoros will work with you to enable full site HTTPS using the existing SSL certificate. The steps required on your part are identical for customers using mixed mode.
Can I wait?
Not for much longer. Khoros is phasing out support for HTTP communities after 18.7, following best practices and maintaining our commitment to securing customer data.
Can I generate my own certificate?
Contact support or your account team for alternative SSL certificate scenarios. Note that alternative scenarios generally carry a charge and require an engagement (SOW). We typically advise against this direction.
What about external domains?
Anything hosted on the community will support HTTPS. However, any references to external domains will require that those domains be under SSL. If you’re using an external asset and the domain does not support HTTPS, we recommend that you upload the asset to your community via studio then update the reference code/URL.
What is a SAN SSL certificate?
See the What is the SAN SSL certificate? Article.
What are the benefits of using SSL (HTTPS encryption)?
See the Full HTTPS Encryption for all Communities article.
Thank you for your time and we look forward to working with you to migrate you to HTTPS!
In 2018 Khoros is moving all customer sites to SSL encryption (HTTPS) to safeguard customer data. HTTPS encrypts all data passed between the end user and your community. Khoros is ready to work with you to enable, test, and deploy a SSL certificate, to bring your community to full HTTPS delivery. We will also be sending out email notifications to our customers over the next month and a half as a reminder on this.
These changes will result in:
Note that the steps below follow Khoros Standard SSL deployment. Access to Standard SSL deployment is included with existing customer licenses (is free).
To get started, we ask that you follow the following steps.
Why is Khoros switching to HTTPS now?
Major browser and search vendors are making changes to flag pages that are delivered over HTTP as 'not secure' after July 2018. Obviously, this kind of message is not one you want associated with your brand. HTTPS is also a factor in search engine ranking. It's presumed that search vendors will add additional weight to HTTPS in their ranking formula this year.
What if part of my community is delivered over HTTPS already?
For customers using "mixed mode", Khoros will work with you to enable full site HTTPS using the existing SSL certificate. The steps required on your part are identical for customers using mixed mode.
Can I wait?
Not for much longer. Khoros is phasing out support for HTTP communities after 18.7, following best practices and maintaining our commitment to securing customer data.
Can I generate my own certificate?
Contact support or your account team for alternative SSL certificate scenarios. Note that alternative scenarios generally carry a charge and require an engagement (SOW). We typically advise against this direction.
What about external domains?
Anything hosted on the community will support HTTPS. However, any references to external domains will require that those domains be under SSL. If you’re using an external asset and the domain does not support HTTPS, we recommend that you upload the asset to your community via studio then update the reference code/URL.
What is a SAN SSL certificate?
See the What is the SAN SSL certificate? Article.
What are the benefits of using SSL (HTTPS encryption)?
See the Full HTTPS Encryption for all Communities article.
Thank you for your time and we look forward to working with you to migrate you to HTTPS!