https://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022016-09-16T10:19:15ZThe Document Foundation RedmineInfrastructure - Task #2039: tdf.io needs a certificatehttps://redmine.documentfoundation.org/issues/2039?journal_id=105352016-09-16T10:19:15ZFlorian Effenbergerfloeff@documentfoundation.org
<ul></ul><p>The (mid-term) plan was to go with StartSSL wildcard certificate for the <br />main sites and try Let's Encrypt for other VMs. Sounds like an ideal <br />test case for the latter one - Dennis, would you like to give Let's <br />Encrypt a try on this?</p>
<p>I know it's only valid for 90 days, but would make a good test case.</p> Infrastructure - Task #2039: tdf.io needs a certificatehttps://redmine.documentfoundation.org/issues/2039?journal_id=137832017-11-21T16:18:57ZGuilhem Moulinguilhem@libreoffice.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>Guilhem Moulin</i></li></ul><p>Oops wasn't aware of this ticket. <a class="external" href="https://tdf.io">https://tdf.io</a> is available since mid January, and distributing to <a class="external" href="https://tdf.io/$shortlink">https://tdf.io/$shortlink</a> should be preferred over their <a class="external" href="http:// counterpart">http:// counterpart</a>. They both 301-redirect to the location set in the YOURLS database. OTOH <a class="external" href="http://tdf.io/admin">http://tdf.io/admin</a> 301-redirects to its <a class="external" href="https:// counterpart">https:// counterpart</a> in order to protect logins.</p>
<p>Moreover since about 2-3 weeks YOURLS uses SAML 2.0 for authentication: unauthenticated users are redirected to the central auth portal, and then back to <a class="external" href="https://tdf.io/admin">https://tdf.io/admin</a> after authentication.</p>