No image

Extradium 2010 v2.5.4.0: New Auto Sign In feature

A lot of customers have lately started to tell us that the standard Extradium Sign In Web Part (see below) really doesn’t cut it for internal users.

And they’re right. For an internal user who is already authenticated on the network, having to click on “Sign in with Windows credentials” on an extranet site hosted in their domain (or trusted by the DMZ domain) is a bit cumbersome, if not annoying.

In the latest version of Extradium 2010 (v2.5.4.0), we have finally decided to provide a solution for those customers, based on OrbitOne’s SharePoint 2010 automatic sign-in project on CodePlex.

Now, why don’t we just recommend our customers to use that solution instead of embedding it in our product? For 3 basic reasons:

  1. We think it’s more convenient for our customers (and the deployment is a bit more easier – see below)
  2. OrbitOne’s solution relies on a custom sign in page, which conflicts with Extradium’s own default sign in page.
  3. We wanted to offer more flexibility, even in “anonymous” scenarios, where the top-level site is anonymous and secured content is available in sub-sites (or other site collections). That’s why the code that performs the auto sign in runs in the context of Extradium’s Sign In Web Part, not just Extradium’s Sign In Page.

How do I set it up?

It’s easy: just install or upgrade your current installation of Extradium. There is no need to register OrbitOne’s custom PowerShell commandlet, as it relies in the SharePoint PowerShell Registration folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration)

How do I configure it?

This piece is completely similar to OrbitOne’s solution, so you’ll have to run a few PowerShell commands to configure your auto sign in settings:

  1. First, retrieve the sign in configuration object:

    $config = Get-SPSignInConfiguration -webapplication https://[yourwebappurl]

  2. Add a mapping (the first parameter must define an IP address sub-mask and must therefore end with at least one star):

    $config.ProviderMappings.Add(“192.168.20.*”,”Windows Authentication”) or better:

    $config.ProviderMappings.Add(“192.168.20.*”,”AD”) if you’re using an non-English version of SharePoint.

    $config.Update()

  3. To remove a mapping:

    $config.ProviderMappings.Remove(“192.168.20.*”)

    $config.Update()

  4. To clear all mappings:

    $config.ProviderMappings.Clear()

    $config.Update()

  5. To view all mappings:

    $config.ProviderMappings

If you need more information, please take a look at the CodePlex documentation or write us at https://support.riolinx.com.

facebooktwitterredditlinkedinmailby feather