Recommended Posts

Building on the work done with the Neowin External Login Tool (NELT), I've rebuilt a set of ASP.NET classes which will allow you to integrate the NELT functionality into your own ASP.NET websites.

Let's get some explaining done; The Neowin Login Services library is a .NET implementation of the external Neowin.net authentication mechanism. The mechanism is as follows:

1. Check for an existing login ticket.

1.a. If one does not exist, forward the user to Neowin.net where they can log in.

1.b. After a succesful login, redirect the user back to the website, with a ticket id.

2. Check the validaty of the ticket using the CheckTicket service provided by Neowin.net

2.a. If the ticket is valid, retrieve the available user details.

This specific implementation deals with this a specific way:

1. An IHttpModule which checks to see if the ticket exists. If the ticket does not exist, this module will forward the user to the Neowin.net external login script. This is built as a module so that its functionality can be automatically be called if the presence of a RequireLoginAttribute is decorating the page class:

[RequireLogin(true)]
public class _Default : System.Web.UI.Page...

2. After a succesful login, Neowin.net will redirect to an IHttpHandler, "Neowin.axd", that will check the validaty of the ticket, and store it in Session. This is built as an IHttpHandler so that functionality, such as Login and Logout can be called at the user request.

3. Parse the response from Neowin.net, and create an instance of NeowinUser which stores the currently authenticated user.

NELT.NET 2.0 stores the authentication in Session, this is to minimise the number of requests needed to be sent to Neowin, and to keep wait times to a minimum.

There are some required configuration changes that need to be made to your web.config in order to use NELT functionality:

1. Enable the configuration by declaring a configuration section (in a group called neowin.net).

	<configSections>
		<sectionGroup name="neowin.net">
			<section name="login" type="Neowin.LoginServices.Configuration.LoginServicesConfigurationSection, Neowin.LoginServices"/>
		</sectionGroup>
	</configSections>

2. Configure the NELT library.

	<neowin.net>
		<login baseUrl="http://localhost/NeowinLoginServices/" imageUrl="http://neowin.fidelitydesign.net/resources/neowin_examplelogin.png"/>
	</neowin.net>

The configuration element allows (currently) two properties. The base url that will be used to both redirect after login, and redirect to the Neowin.axd handler for verification. The image url, is the (as it reads) url for the image that will be displayed on the Neowin external login page.

3. Reference the IHttpHandler and IHttpModule in either the system.web (IIS6 & IIS7 Classic .NET), or system.webserver (IIS7 Integrated)

IIS6 & IIS7 Classic .NET

	<system.web>
		<httpHandlers>
			<add verb="GET" path="Neowin.axd" type="Neowin.LoginServices.LoginServicesHandler, Neowin.LoginServices"/>
		</httpHandlers>
		<httpModules>
			<add name="LoginService" type="Neowin.LoginServices.LoginServicesModule, Neowin.LoginServices"/>
		</httpModules>
	</system.web>

IIS7 Integrated

	<system.webServer>
		<modules>
			<add name="LoginService" preCondition="managedHandler" type="Neowin.LoginServices.LoginServicesModule, Neowin.LoginServices"/>
		</modules>
		<handlers>
			<add name="LoginService" preCondition="integratedMode" verb="GET" path="Neowin.axd" type="Neowin.LoginServices.LoginServicesHandler, Neowin.LoginServices"/>
		</handlers>
	</system.webServer>

After that (and of course adding the reference to Neowin.LoginServices.dll), you are good to go. You can access the current Neowin.net user in code:

NeowinUser user = NeowinUser.GetUser();
if (user != null)
{
  // Logged in code here
}
else
{
  // Perhaps log in?
  Response.Redirect("Neowin.axd?action=login");
}

The IHttpHandler includes functionality for both logging in and logging out. To login, redirect your users to ~/Neowin.axd?action=login, to logout, redirect your users to ~/Neowin.axd?action=logout. Any other action will simply redirect back to the application base url.

As I stated previously, any Page that has been decorated with the RequireLoginAttribute, the login system will automatically be started if no valid ticket currently exists.

I hope you all find this useful, if you need any help integrating this, let me know.

Whats next? I hope to be able to build an ASP.NET MVC compatable library for those wanting to implement URL rerouting, etc. Also, I might ask the Neowin.net development staff to include more properties, such as a url to the user's avatar.

Ideas? If you have any, let me know!

Source code? If you are interested in the source code for this library, I'll be more than willing to share (need to finish development notes etc.)

Neowin.LoginServices.zip

Edited by Antaris
Link to comment
https://www.neowin.net/forum/topic/736472-neowin-login-services-neltnet-20/
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • There is a huge portion of the Windows users who use a cooperate provided computer, which means they are using an organization provided username and not a Microsoft username. Also, they users may not be allowed to install a 3rd party browser, so this would be perfect for them.
    • COBOL itself is not the problem. Code that has been bodged and kludged over decades but still somehow runs is probably the sort of Gordian knot that even AI can't necessarily unravel.
    • Nice devices but my Surface Pro 9 got bricked from a Windows Update efter only three years. Never buying a device from MS again.
    • Icaros Shell Extensions 3.3.6 by Razvan Serea Icaros is a collection of lightweight, high quality, Windows Shell Extensions. Icaros can provide Windows Explorer thumbnails, for essentially any video media format supported by FFmpeg, this includes popular filetypes such as: Mkv, Flv, Avi, Mp4, Mov, Rmvb, M2ts, Ogm etc. Besides the FFmpeg supported filetypes, Icaros also contains custom parsers, which can produce Cover Art thumbnails for Mkv, Flac, Ape, Mpc and several other filetypes. Icaros also provides Windows Explorer properties for the following popular filetypes: Mkv, Mk3d, Mp4, Mov, Webm, Ogm, Ogg, Flv, Avi, Rm, Rmvb, Flac, Opus, Spx, Ape, Mp3, Mpc, Mka, Tak, Tta, Ofr, Wav and more. Properties refer to the info shown for each file in Explorer, such as length, width, height, title, channels and so on. Icaros works on Vista, Windows 7, Windows 8/8.1, Windows 10 and Windows 11. Icaros Shell Extensions 3.3.6 changelog: Added support for Animated WEBP thumbnailing Added support for UTF-8 filenames in CBX files (Comic book files) Added support for rotation of MKV thumbnails Added support for "Sort title" property in MKV files Fixed some wav files not showing properties Fixed some old h264 files producing green thumbnails Fixed default level of MKV tags (now set to 50) Updated FFmpeg Download: Icaros Shell Extensions 3.3.6 | 12.8 MB (Freeware) Download: Portable Icaros 3.3.6 View: Icaros Shell Extension Home Page | Screenshots 1 | 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      72
    4. 4
      Michael Scrip
      64
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!