I have IIS 7.5 installed. How can I configure a virtual directory so that it authenticates users against an instance of AD FS 2.0? I've tried modifying my web.config in a similar fashion to the way I modified it to work with C# web applications, but to no avail.
How I have my federated structure configured is The Local web server applications are located on Server 1, The Web server/Federation Proxy (Remote Access/Web Proxy Server) are located on Server 2, IIS is installed on both Server 1 and Server 2. SSL Port on Server 2 is the default (443). SSL Port on Server 1 is (465**){those are not actually the * character}. Server 2 (The server that actually receives the web requests from outside of the domain) Has Virtual directories located in the default inetpub folder. In IIS I redirect the virtual folder to The application on Server 1 (so if the application name on server 1 is server1.domain.com/AppliactionOne, the virtual directory on Server 2 is Named {/ApplicationOne} and is accessible from the address or domain you have forwarded in your external dns {external-address-or-domainName-for-server-2.com/ApplicationOne}. When setting up the forwarding address you need to forward the port for the address you configured in your router to Server 1 {https://external-address-or-domainName-for-server-2.com:465/ApplicationOne} and open the port on Server 1 external-address-or-domainName-for-server-2.com:465/ApplicationOne
This way the external Server 2 is still communicating authentication with the federation server. just be sure to set the reply address in your claims to have the port number configured for Server 1 and the same certificate installed as on your Server 2 Server.
Related
I am deploying a React app on a virtual machine, windows server 2012, hosted on the IIS server. The website is successfully running on the local server. When I try to access the website through a remote computer, the static components are rendered successfully, but the API doesn't work. The API is written in node.js and installed as a windows service on the windows server with the port number 5000.
I put localhost:5000 as the axios base url in react. But when I try to access from the remote computer, the computer is reading from its own localhost instead of the server's localhost.
Even if I change the axios base url from localhost to the server's ip address, it still cannot read the API properly.
My questions are as follows:
How to make the remote computer reads from the server's localhost without putting the server's ip address?
How to make the local server's windows service accessible to other computers?
What is the best practice to store the API base url in React in production? (store in.env, config, etc...)?
I just solve the issue and I post the answer here for anyone who has the same issue.
Windows
Create a firewall rule (Windows only)
You need to allow other computers to connect through your firewall.
Open the Windows Firewall
Go to “Inbound Rules”
Click “New Rule”
Select “Port” to make a port rule
Under “Specific local ports”, enter 80 and 8000 (for me it's port 5000)
Select “Allow the connection”
Click “next” then choose a name for your rule.
Source of this answer: [https://otree.readthedocs.io/en/latest/server/adhoc.html#windows][1]
I deplyoed my nodejs application on a AWS server with windows server as OS. The application is a simple express server running on https port 443. The application is accessible through localhost, but I can access the app through public IP.
Here are a few things I tried:
IIS with urlrewrite like so (https://dev.to/massivebrains/deploying-node-express-app-on-a-windows-server-2l5c)
iisnode
I am still not able to access my app. I setup up inbound rules in my firewall for the port and nodejs itself.
The issue was simply in my security group. I had set up the IP addresses I was expecting, but one was missing. It is working now.
We have an VisualSVN Server running on our development server. An external vendor needs to access / use it (primary via TortoiseSVN, sometimes by using the web interface).
Since our IT does not allow external access to internal servers, they need to use a webserver in the DMZ (Demilitarized Zone).
Is there a way to redirect the external SVN access from this DMZ-webserver to the internal development server (preferable by using IIS 7 on the DMZ server)
I have two servers. First one is a server with ASP app on it and the second one is an LDAP auth server. I need to login on app server over LDAP on the second server and I need to use windows auth (NTLM or Negotiate). As I know based on my research to login on the server using active directory domain from other server they must be in the same local network. This can be established by VPN. But the thing is that I can't use a VPN. Can it be established somehow? I'm currently trying to configure IIS to not identify my user on my current domain and serve the credentials to remote server over LDAP using .Net. Sorry if I have a wrong understanding about something, I'm still newbie in windows auth and AD. Correct me if I wrong in something.
I'm using ASP.NET Core RC2 and IISExpress 10 on my local machine and my target framework is 452 due to using some old modules.
On remote app server I'm using IIS 8.5
I hosted a website on IIS, running on port 81. I can access it on the server machine from http://localhost:81/test.aspx.
I also can establish a remote desktop connection to the server, using its ip adress server-ip.
Now I want to access the web site using my PC (or any other PC). However, I type type http://server-ip:81/test.aspx on my web browser and the page is not loaded.
I've already opened port 81, by adding a new inbound rule to the server's windows firewall. The exception for World Wide Web Services (HTTP) is also ticked on. I even shut down the firewall entirely, but I still can't access the web site remotely.
Can somebody tell what the problem may be? Thanks in advance.