khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-02 17:59:36 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #372 from owncloud/admin-guide-trusted_domains

Browse Source 
Admin guide: clarify trusted_domains
This commit is contained in:
Morris Jobke
2014-06-06 09:57:30 +02:00
parent 3464678391 5d0c8ced75
commit d42d62567f
2 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
admin_manual/installation/images/untrusted-domain.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 26 KiB

12
admin_manual/installation/installation_wizard.rst
View File

@@ -97,16 +97,20 @@ Note
~~~~
ownCloud will take the URL used to access the Installation Wizard and insert
that into the config.php file for the ‘trusted_domains’ setting.
All needed domain names of the owncloud server go into the
'trusted_domains' setting. No domain names of clients go there.
Users will only be able to log into ownCloud when they are using a domain name
listed in the ‘trusted_domans’ setting.
Users will only be able to log into ownCloud when they point their browsers to a
domain name listed in the ‘trusted_domains’ setting. An IPv4 address can be
specified instead of a domain name.
In the event that a load balancer is in place, there will be no issues, as long
as it sends the correct X-Forwarded-Host header.
It should be noted that the loopback address, 127.0.0.1, is whitelisted and
It should be noted that the loopback address, '127.0.0.1', is whitelisted and
therefore users on the ownCloud server who access ownCloud with the loopback
will successfully login. In the event that an improper URL is used, the
interface will be able to successfully login.
In the event that an improper URL is used, the
following error will appear:
.. image:: images/untrusted-domain.png