Basic Webserver Behind Azure AD Authentication

Posted by denismcapple@reddit | sysadmin | View on Reddit | 3 comments

Hello Sysadmins! I am trying to find the best way to host very small little websites, for customer facing data generated from a piece of software. I'd need access to be secured by Azure AD Authentication. Basically, this software generates output (3D Models) in the form of a small folder structure containing a .html, a few .js and .css files, and a subfolder with some png's. Ideally, i'd like to be able to stand up some sort of server which can host multiple sites within it - and then tie access to those sites, to Azure AD Guest accounts. Anyone have any ideas of something that can do this? I've read about Azure Static Web Apps - but it seems overly complicated. Hoping for something pretty basic and simple here. Any advice muchly appreciated! Cheers 

3 Comments

[-]

MrYiff@reddit

If the app is just HTTP based then you could use an Azure AD (no Entra I guess), App Proxy. You just need to run a small agent service somewhere in the same network as your website and then you can setup the App Proxy and everything gets tunnelled through Azure first (so no need to mess with any firewall rules or open ports), and you can have the option to require Azure AD authentication first. https://learn.microsoft.com/en-us/azure/active-directory/app-proxy/application-proxy

mjcl@reddit

If you're comfortable with Linux, I've used [oauth2-proxy](https://github.com/oauth2-proxy/oauth2-proxy) with nginx to add Azure AD auth to an existing webapp. It'd be pretty easy to setup nginx to serve static files directly.

denismcapple@reddit (OP)

This looks like a good option - Do you think it's possible to redirect certain users to certain internal URLs? For example: [usera@domain.com](mailto:usera@domain.com) after authentication is passed to [http://internal.webserver/siteA](http://internal.webserver/siteA) [userb@domain.com](mailto:usera@domain.com) after authentication is passed to [http://internal.webserver/site](http://internal.webserver/siteA)B and so on?

Reply to Post

3 Comments