I have a dream

I have a dream. A dream of using my machine with seamless background updates without worrying about the restarts. A dream of using any device without worrying about drivers. A dream to connect projectors, speakers, power plugs without carrying additional adapters. A dream to connect my headphones to any phone, any in-flight system without thinking about splitters and connectors. A dream to use a single USB spec cable with all devices. A dream to collaborate with my colleagues without thinking about collaborating software (and its resource utilization). I have a dream.

Collaboration: Outlook, Teams, Telegram, Slack, WhatsApp, Skype, Skype for Business

i-have-a-dream-collaboration

Adapters: US, Europe, Japan, Asia and what not

photo_2018-10-11_07-23-48

Headset/Speakers: 2.5mm/3.5mm and splitter for in-flight systems

photo_2018-10-11_07-23-51

Adapters/Dongles: USB-C/Mini Display to various formats and network connections

photo_2018-10-11_07-23-54

Namaste,
Mayur Tendulkar

Advertisements

Claims Based Authentication for SharePoint 2010–Part II

In my previous post, I talked about how to enable Claims Based Authentication. In this post, I’ll talk about one more aspect of it – Forms Based Authentication (FBA). FBA can be helpful for creating internet facing, public sites which can be accessed by millions of users who can’t be part of your Active Directory infrastructure.

ASP.NET when launched supported 3 types authentications namely: Windows Authentication (better for Intranet scenarios and credentials are stored inside Active Directory), Passport Authentication (Now Live ID Authentication, can be used via Claims Based Authentication) & FBA (where user data is maintained inside SQL Database). ASP.NET 2.0 provided some tools and classes and made FBA much more simpler. It automatically created required tables, stored procs, UI to manage Users (Membership Providers), their access rules by their roles (Role Provider) and store some more data about users (Profile Provider).

These tools and classes are available within SharePoint Server. To configure SharePoint for FBA follow the steps mentioned below:

STEP01: Creating a database and schema for FBA

First create a blank database in SQL Server Management Studio (e.g  test1.tendulkar.db). To configure this database with FBA, run command prompt at elevated privileges an run following command:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql

This will open up a ASP.NET SQL Server Setup Wizard. Here click next and choose ‘Configure SQL Server for application services’. Now, the window will look something like below:

fba3

This process will create all the required tables, views, stored procedures for above mentioned providers.

fba4

STEP02: Configure FBA inside IIS

Execute start –> run –> inetmgr

fba6

Here, you’ll see different web applications along with ‘SharePoint Central Administration’ and ‘SharePoint Web Services’ application. Please note highlighted sections.

In SharePoint Central Administration first add Connection String. You’ll see a window something like below:

fba5

After that, in Providers, add Roles Provider and for that matter, you should get following window

fba7

Now, add Membership provider and window will look like image mentioned below

fba8

Now, add Profile provider

fba9

Repeat this process for SharePoint Web Services web application as well.

STEP03: Enable FBA for Web App

When you created Web Application, if you’ve selected Claims Based Authentication, go back to SharePoint Central Administration and select your Web Application. On ribbon, click on Authentication Providers and select Default. This will bring in your Web App settings window. Here, pass-on our just configured providers.

fba10

Now repeat the step (02) of creating Connection, Role Provider, Membership Provider and Profile Provider for this application in IIS.

Remember, these providers needs to be present at 3 locations, i.e. a) Central Administration, b) Web Services and c) your Web App

Now, create roles and users for this application inside IIS. Once you’re done with it, create site collection for Web App. After you create a site collection and navigate to browsing, it will give following options:

fba11

It will bring in the default sing-in page. Provide your use credentials and log in. Once you log-in you’ll be able to see the custom FBA login name at top.

fba12

I hope, this will help you to get started. In my next post we’ll go deeper into this FBA stuff and also we’ll try Claims Based Authentication using Trusted Identity Providers.

Namaste

Mayur Tendulkar | www.mayurtendulkar.com

Other References: