View Attach (4) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 Clipboard01.png 402.2 kB 1 29-Dec-2020 05:25 Ben Spink
png
 Clipboard02.png 554.7 kB 1 29-Dec-2020 05:25 Ben Spink
png
 Clipboard03.png 280.2 kB 1 29-Dec-2020 05:25 Ben Spink
png
 Clipboard04.png 157.6 kB 1 29-Dec-2020 05:25 Ben Spink

This page (revision-19) was last changed on 29-Dec-2020 05:25 by Ada Csaba

This page was created on 29-Dec-2020 05:25 by Ada Csaba

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed one line
When multiple domains point to same host, user accounts can be restricted to a certain domain only, following these steps:
When multiple domains point to same host, user accounts can be restricted to a certain domain only, following these steps:\\
\\
- change the HTTP server item's User Connection Group to @AutoHostHttp on Preferences -> Ip/Servers page\\
- add new user connection groups named as the domain FQDN (wst0.intranet.local and wst0.intranet2.local in this example)\\
\\
[attachments|Clipboard01.png]\\
\\
- add new login page entries on Preferences -> Webinterfcace page, Options panel, as the domain FQDN prepended with an asterisk (*)\\
\\
[attachments|Clipboard02.png]\\
and/or\\
[attachments|Clipboard03.png]\\
It is the __critical__ condition the login html file __stem__ to match the exact domain name, and the __Connection Group__. The extension must always be __.html__. As per above example __wst0.intranet.local.html__ and __wst0.intranet.local__. \\
\\
It is not mandatory the actual login html files to exist, but if these do, can be customized for each domain to have it's own custom look and feel. For that, duplicate the original login.html file, change the logo reference, CSS code, etc. Careful not to remove any critical HTML tags or script components.\\
\\
Now we can select a User Connection group in User Manager and add user accounts into. These accounts will be restricted to log only when accessing one of these domain URLs.\\
\\
[attachments|Clipboard04.png]\\
\\
A special use case of usage is when only one CrushFTP server instance is used as a forward [FTPProxy] in front of multiple FTP servers belonging to different domains. You need to add a template account into each user connection group set up as described in this article.\\
At line 3 changed 18 lines
- change the HTTP server item's User Connection Group to @AutoHostHttp on Preferences -> Ip/Servers page
- add new user connection groups named as the domain FQDN ( wst0.intranet.local and wst0.intranet2.local in this example)
[clipboard01.jpg here]
- add new login page entries on Preferences -> Webinterfcace page, Options panel, as the domain FQDN prepended with an asterisk (*)
[clipboard02.jpg here] and/or [clipboard03.jpg here]
Now we can select a User Connection group in User Manager and add user accounts into. These accounts will be restricted to log only when accessing one of these domain URLs.
[clipboard04.jpg here]
A special case of usage is when only one CrushFTP server instance is used as a forward proxy in front of multiple FTP servers belonging to different domains. We need to add a template account into each user connection group set up as described in this article
http://www.crushftp.com/crush7wiki/Wiki.jsp?page=FTPProxy
Another special use case is integrating this setup within a DMZ scenario. In this situation we'll need to create and assign on the internal server an loopback port item for each domain connection group ( like port 8080 for wst0.intranet.local and port 8081 wst0.intranet2.local following the above example). On the DMZ node we create the same login.html entries on Preferences->Webinterface->Options page, as above, create the domain connection groups on Preferences->IP/servers page and in User Manager we add an 'template' account into each . The template accounts should have their VFS item pointed to the corresponding loopback HTTP port item . The public facing HTTP port item on DMZ has to be assigned to the @AutoHostHTTP connection group.\\
\\
Version Date Modified Size Author Changes ... Change note
19 29-Dec-2020 05:25 2.43 kB Ada Csaba to previous
18 29-Dec-2020 05:25 2.429 kB Ada Csaba to previous | to last
17 29-Dec-2020 05:25 2.423 kB Ada Csaba to previous | to last
16 29-Dec-2020 05:25 2.498 kB Ada Csaba to previous | to last
15 29-Dec-2020 05:25 2.387 kB Ada Csaba to previous | to last
14 29-Dec-2020 05:25 2.381 kB Ada Csaba to previous | to last
13 29-Dec-2020 05:25 2.073 kB Ada Csaba to previous | to last
12 29-Dec-2020 05:25 2.072 kB Ada Csaba to previous | to last
11 29-Dec-2020 05:25 2.044 kB Ada Csaba to previous | to last
10 29-Dec-2020 05:25 2.091 kB Halmágyi Árpád to previous | to last
9 29-Dec-2020 05:25 2.089 kB Halmágyi Árpád to previous | to last
8 29-Dec-2020 05:25 1.869 kB Ada Csaba to previous | to last
7 29-Dec-2020 05:25 1.113 kB Ben Spink to previous | to last
6 29-Dec-2020 05:25 1.13 kB Ben Spink to previous | to last
5 29-Dec-2020 05:25 1.13 kB Ben Spink to previous | to last
4 29-Dec-2020 05:25 1.125 kB Ben Spink to previous | to last
3 29-Dec-2020 05:25 1.113 kB Ben Spink to previous | to last
2 29-Dec-2020 05:25 1.106 kB Ada Csaba to previous | to last
1 29-Dec-2020 05:25 0.344 kB Ada Csaba to last AutoHostHttp
« This page (revision-19) was last changed on 29-Dec-2020 05:25 by Ada Csaba
G’day (anonymous guest)
CrushFTP10 | What's New

Referenced by
IP Servers

JSPWiki