Skip to content

Instantly share code, notes, and snippets.

@khalidabuhakmeh
Last active January 10, 2017 09:49
Show Gist options
  • Save khalidabuhakmeh/84bf31fb2699a7746729 to your computer and use it in GitHub Desktop.
Save khalidabuhakmeh/84bf31fb2699a7746729 to your computer and use it in GitHub Desktop.

Problem

We would like to secure sites hosted on IIS that may / or may not be written with ASP.NET. Additionally, these sites may not be applications we have complete control over (OSS project).

Proposed Solution

An OpenID Connect HttpModule client that can be added to any IIS hosted application via web.config and offer crude authentication. Crude authentication means setting a few basic rules in app settings: endpoints and claims. This would work with an ASP.NET application, NodeJs application, etc. Anything that can be hosted on IIS.

How This Problem Came About

We have a simple site that has a single web interface with minimal routes and should only be accessible to what we deem as Administrators. The application could be made OSS, but we are forced to keep it private because we layered our authentication dependency into the application.

@jonas-stjernquist
Copy link

I'm currently also thinking about developing a OIDC HTTP module, have you made any progress yet and have you experienced any issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment