iMIS Single Sign On Options

There are a number of ways implement single sign on with iMIS.  Here I'll list each approach along with the pros and cons of each.

MembershipWebService.asmx
    Pros

1.         Available with iMIS out of the box
2.         Accessible via any language that can call soap web services

    Cons

1.         Only works in the same domain / sub domain
2.         The 3rd party site is required to provide a login screen.
3.         The users credentials will be exposed to the 3rd party site as the user will be required to enter them                     into the 3rd party's login form.
4.         It is an older technology based on SOAP


5. Share Machine Key

    Pros

1.         ​Only works between asp.net / mvc applications

    Cons

1.         Only works in the same domain / sub domain
2.         You have to share the same "key" across all web applications which could be 3rd party site


3. Roll you own

    Pros

1.         I can't think of any

    Cons

1.         Cost of development
2.         Security risk if not done properly

Other Single Sign On Solutions on the market
    Pros

1.         No need for a custom solution

    Cons

1.         The ones that I know of all use older technology based on SOAP.
2.         They don't implement modern standard protocols


3. Organized Bits iMIS Identity Server
4.     Pros
5.         Implements modern standard protocols.
6.         It uses RESTful endpoints.
7.         It is an iPackage install into iMIS.
8.         It supports multiple types of client applications (Web, SPA, mobile, and desktop)
9.         3rd party sites do not have access to the members credentials thereby ensuring security.
10.         It supports the iMIS Facebook login functionality.

    Cons

1.         I honestly don't know of any.