I did this back in the day so thought it would be a good idea to write up.
Classic ASP is basically just static HTML files, no web.config, no ASP pipeline, no code behind etc.
And they are still out there.
So we will integrate it with ADFS using WIF i.e. everything is driven by a web.config.
Which means we need to add one - example in this gist.
To test this, I used a Windows 8 PC.
This PC has both WIF 3.5 and WIF 4.5 installed. WIF 4.5 is built into ASP.NET 4.5.
So you may need to install this.
This is the line in the web.config:
section name="microsoft.identityModel" type="Microsoft.IdentityModel.Configuration.MicrosoftIdentityModelSection, Microsoft.IdentityModel, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Also WIF doesn't run on Server 2003 - hopefully you've upgraded by now :-)
The key to getting WIF to be added to the pipeline is this line:
Note that the logging at the end is optional and this part of the file can be removed if not required.
All the above has to be done "on the fly". There is no way to create a Classic ASP project in Visual Studio. (In fact, Microsoft go out of their way to actively discourage this. The official line is that Classic ASP is no longer supported). Consequently, there is no context checking, intellisense or compile / run phase.
I didn't use VS at all - just Notepad++.
Also remember to enable ASP under Windows Features / IIS / World Wide Web Services / Application Development Features.
And you can't use an classic Application Pool in IIS - it needs to be integrated.
I just took a folder on my local PC and added a Default.asp (which contained some basic HTML) and the web.config.
Then I added this as an application in IIS. I called the application "ClassicASPBasic".
I then configured an RP on ADFS. There is no metadata so it easiest to do this manually.
Then configure the web.config. You just need to alter the "my-adfs" to your ADFS FQDN and "my-pc" to wherever you have the website hosted.
Also remember to update the thumbprint with your ADFS token-signing certificate.
Then in IIS on the RHS - "Browse Application" - use the port 443 link.
IIS sees the web.config. The web.config tells it to use the WIF classes. WIF by default protects everything so it sends you off to ADFS to authenticate. Authenticate and you are redirected back to the simple .asp page.
The next step is to Sign Out. You cannot use the standard WIF FederatedSignOut messages because there is no .NET framework so it has to be done via a URL link on the page. If you want the user to end up on the ADFS logout page, use:
<a href="https://my-adfs/adfs/ls/?wa=wsignout1.0">Sign out</a>
If you want to the user to be redirected back to the application use:
<a href="https://my-adfs/adfs/ls/?wa=wsignout1.0&wreply=https://xxx/yyy/Logout.asp">Sign out and return</a>
- xxx is the ADFS URL
- yyy is the application URL
- Logout.asp is a new page added to the site
The other way is to use VS and create an MVC application. Refer How To: Build Claims-Aware ASP.NET MVC Web Application Using WIF.
Then simply copy all your static files over.
This way allows you to access the claims as per the link.