115 lines
2.6 KiB
Markdown
115 lines
2.6 KiB
Markdown
|
Sharepoint-Seite im Apache veröffentlicht
|
|||
|
|
|
|||
|
|
Donnerstag, 20. Juni 2019
|
|||
|
|
|
|||
|
|
11:06
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
Heute stand ich vor der Aufgabe, dass unsere interne Sharepoint-Seite im Apache veröffentlicht werden sollte. An sich hätte das kein Problem sein sollen -- war es im Endeffekt aber.
|
|||
|
|
|
|||
|
|
Bei uns schaut es schematisch so aus, dass der Apache alle Anfragen anhand des Domain-Namens auf die virtuellen Server weiterreicht bzw. als Proxy fungiert: Internet -\> Apache / DMZ -\> Virtueller Host / Backend Server.
|
|||
|
|
|
|||
|
|
Anhand [des Blog-Eintrags von Todd Klint](http://toddklindt.com/blog/Lists/Posts/Post.aspx?ID=39) den Sharepoint-Service so eingerichtet, dass er auf die richtige URL lauscht. Die Konfigurationsdatei des virtuellen Hosts sah dann folgendermaßen aus:
|
|||
|
|
|
|||
|
|
<table>
|
|||
|
|
<colgroup>
|
|||
|
|
<col style="width: 8%" />
|
|||
|
|
<col style="width: 91%" />
|
|||
|
|
</colgroup>
|
|||
|
|
<thead>
|
|||
|
|
<tr class="header">
|
|||
|
|
<th><p>1</p>
|
|||
|
|
<p>2</p>
|
|||
|
|
<p>3</p>
|
|||
|
|
<p>4</p>
|
|||
|
|
<p>5</p>
|
|||
|
|
<p>6</p>
|
|||
|
|
<p>7</p>
|
|||
|
|
<p>8</p>
|
|||
|
|
<p>9</p>
|
|||
|
|
<p>10</p>
|
|||
|
|
<p>11</p>
|
|||
|
|
<p>12</p>
|
|||
|
|
<p>13</p>
|
|||
|
|
<p>14</p>
|
|||
|
|
<p>15</p>
|
|||
|
|
<p>16</p>
|
|||
|
|
<p>17</p>
|
|||
|
|
<p>18</p>
|
|||
|
|
<p>19</p>
|
|||
|
|
<p>20</p>
|
|||
|
|
<p>21</p>
|
|||
|
|
<p>22</p>
|
|||
|
|
<p>23</p>
|
|||
|
|
<p>24</p>
|
|||
|
|
<p>25</p>
|
|||
|
|
<p>26</p>
|
|||
|
|
<p>27</p>
|
|||
|
|
<p>28</p>
|
|||
|
|
<p>29</p>
|
|||
|
|
<p>30</p>
|
|||
|
|
<p>31</p>
|
|||
|
|
<p>32</p>
|
|||
|
|
<p>33</p></th>
|
|||
|
|
<th><p><VirtualHost *:443></p>
|
|||
|
|
<p>SSLEngine On</p>
|
|||
|
|
<p>SSLProxyEngine On</p>
|
|||
|
|
<p>SSLCertificateFile "$CERT_FILE"</p>
|
|||
|
|
<p>SSLCertificateKeyFile "$CERT_KEY_FILE"</p>
|
|||
|
|
<p>SSLProxyCACertificateFile "$CERT_CA_FILE"</p>
|
|||
|
|
<p>ProxyRequests Off</p>
|
|||
|
|
<p>ProxyVia On</p>
|
|||
|
|
<p> </p>
|
|||
|
|
<p>ServerAdmin admin@sps.mydomain.com</p>
|
|||
|
|
<p>DocumentRoot $VHOST_DIR/sps/web</p>
|
|||
|
|
<p>ServerName sps.mydomain.com:443</p>
|
|||
|
|
<p>ErrorLog "|rotatelogs.exe $VHOST_DIR/sps/logs/%Y%m%d_ssl_error.log 86400"</p>
|
|||
|
|
<p>CustomLog "|rotatelogs.exe $VHOST_DIR/sps/logs/%Y%m%d_ssl_access.log 86400" common</p>
|
|||
|
|
<p> </p>
|
|||
|
|
<p># AddDefaultCharset ISO</p>
|
|||
|
|
<p>LogLevel debug</p>
|
|||
|
|
<p>ProxyPreserveHost Off</p>
|
|||
|
|
<p>KeepAlive Off</p>
|
|||
|
|
<p> </p>
|
|||
|
|
<p>ProxyPass / <a href="http://backend-srv:8080/">http://backend-srv:8080/</a></p>
|
|||
|
|
<p>ProxyPassReverse / <a href="http://backend-srv:8080/">http://backend-srv:8080/</a></p>
|
|||
|
|
<p> </p>
|
|||
|
|
<p><Proxy *></p>
|
|||
|
|
<p>Order allow,deny</p>
|
|||
|
|
<p>Allow from all</p>
|
|||
|
|
<p></Proxy></p>
|
|||
|
|
<p> </p>
|
|||
|
|
<p><Directory "$VHOST_DIR/sps/"></p>
|
|||
|
|
<p>Order allow,deny</p>
|
|||
|
|
<p>Allow from all</p>
|
|||
|
|
<p></Directory></p>
|
|||
|
|
<p></VirtualHost></p></th>
|
|||
|
|
</tr>
|
|||
|
|
</thead>
|
|||
|
|
<tbody>
|
|||
|
|
</tbody>
|
|||
|
|
</table>
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
Aus \<<https://www.schakko.de/2009/10/05/sharepoint-mit-apache-als-reverse-proxy-veroffentlichen/>\>
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
Gute Anleitung :
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
<https://thesharepointfarm.com/2014/06/sharepoint-apache-mod_proxy/>
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
LetsEncrypt on Debian 9 and Apache
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
<https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-debian-9>
|