IIS 7 and Above
Noob Question: how to link to default page of another website?
Last post Oct 05, 2017 03:34 AM by Yuk Ding
Oct 03, 2017 03:12 PM|Michael Y|LINK
We have two internal applications developed for us, which reside on the same Windows server. These are presented in IIS as separate websites. Each is bound to a unique IP address (the server has multiple NICs).
Our internal DNS points
app1.domain.com to 192.168.0.55
app2.domain.com to 192.168.0.56
We want to have a separate landing page, with some introductory text about each app and a link to both the sites above. I have therefore created a new website in IIS, and added a really simple default.htm landing page, which works fine.
landing.domain.com to 192.168.0.55 (I am using a host header)
What I am now trying to do now is create a link on that landing page to each app. Ideally, we always want users to always use the new landing page, rather than favouring going direct to the app page. How can I do this?
I thought about linking directly to the 'home' page of each app, but now I am confused about this...
In IIS, under 'Default Document' I see the inherited list of files, such as default.htm, default.asp, index.htm, etc, etc.
However, when I browse the root directory of the website, I don't see any of the default document types, such as .htm(l) pages. I only see some xml, asax, and .config files.
How can I make sure users only get to the applications through my landing page, rather than linking to the respective URLs/IPs?
PS: The application itself doesn't show any breadcrumbs (is that the correct phrase?) in the address bar as you begin to use the app - it always stays as abc.domain.com
PPS: After this change, I also plan to reduce the server to a single NIC and use host headers for the landing page only.
Thanks in advance.
Oct 04, 2017 08:07 AM|Yuk Ding|LINK
It looks like you were requiring a SSO page for these two authentication user.The form authentication only allow us to use the internal web page to authenticate user. So if you need to authenticate user from another website, I'm afriad you may need to hard
code the configuration in your web page. IIS itself should not have such a function to authenticate the cookie from other site.
Oct 04, 2017 11:25 AM|Michael Y|LINK
Thanks for the reply. The two sites use Windows authentication - does this have the same problem as forms-based?
The landing page has no authentication, which is fine. Only when clicking on the link to one of the websites, should it prompt for authentication.
Ideally the links to these websites would also be hidden, to prevent users from navigating directly to these sites (or picking them from their history).
Oct 05, 2017 03:34 AM|Yuk Ding|LINK
I think you windows auhtnetication could not run SSO directly. You could even build the landing site as a front-end and use rewrite to achieve the auhtentication.Then when you succee in logging in the landing, the page will be rewritten to these two site.
It is equal to build a reverse proxy with URL rewrite and it will prevent user from accessing the website directly: