Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's Office 365 Admin Blog > Posts > Netcast 65 - I Feel Like a New Man
December 22
Netcast 65 - I Feel Like a New Man

In this episode I cover authentication considerations for extranet environments. I recount a win against Kerberos and I also type like the wind.

MP3 File (Subscribe)

WMV File (Subscribe)

Duration: 35:58


SharePoint Journeys



This comment was automatically approved! Workflows rule!

Todd O. KlindtNo presence information on 12/23/2010 3:02 PM

I "Fell" Like A New Man

The title in the credits of the webcast say "Fell" instead of "Feel." LMAO

I think it is a Freudian slip based on your recent exploits in agility and injury!

Have a great holiday and thanks for all you do for your SharePoint people (even us developers!)
 on 12/23/2010 4:29 PM

Re: I "Fell" Like A New Man

Well that sucks. :)

Todd O. KlindtNo presence information on 12/23/2010 10:38 PM

Multi-Tenancy in SharePoint 2010 

Todd your extranet discussion had no menstion of Multi-Tenancy in SharePoint 2010  as an Extranet option. Why?
 on 1/11/2011 10:58 AM

Todd I put together my own list from your comments would you mind commenting?

 Would you mind commenting on this list

Option 1, Multi-Tenancy in SharePoint 2010  (Spences Harbor stuff)
Advantages include isolation of Data, operational services and management
• Data Each customer’s data should be isolated, or partitioned. We should also consider other aspects here such as where each customer’s data is physically backed up.
• Usage Most SharePoint features are  exposed to end users.
• Administration How sites and data are administered independently
• Single sign ON Users are administered on internal Active Directory but/ firewalled on a different (OU)
• Customizations We need to ensure that Customer A’s customization isn’t shown to Customer B.
• Operations  We will able to report on usage, audit usage, and perhaps most importantly, charge for usage.
• No new Hardware required.  Can safely  co- exist with intranet solutions
• Very Complex to setup
• New technology first offered in Sharepoint 2010
Option 2  FBA and Claims based  authentication in a single web application
• Different data store for authentication SQL server for users
• Single Sign on  because SharePoint 2010 support more that one authentication provider.
• Different FBA setup for each Customer so muilt web application (performance issue)
• Historic issues with Office clients
• Development and custom coding maybe required to set up  users store and management interfaces for user accounts creation, password reset and creation etc may require custom coding.
• Development for different  login pages for claims or FBA. , with custom login page
• No data and service isolation may be an issue.

Options 3  Second Active Directory for external users with one-way trust

• External domain trust internal domain (security)
• Really complicated to configure correctly
• New servers (Share Point and SQL) for external domain          
• People Picker complexity to resolve internal and external users (really complicated)



 on 1/11/2011 11:37 AM

Re: Multi-Tenancy in SharePoint 2010

I didn't cover multi-tenancy because I don't know much about it. I'm not qualified to talk about it yet. :)

Todd O. KlindtNo presence information on 1/11/2011 8:46 PM

Re: Todd I put together my own list from your comments would you mind commenting?

Hi Colin,
That's a good list. It looks good, I don't really disagree with anything. Keep in mind though, I know nothing about multi-tenancy, so you might have made that all up for all I know. :)

Todd O. KlindtNo presence information on 1/11/2011 8:49 PM

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.


Body *

Today's date *

Select a date from the calendar.
Please enter today's date so I know you are a real person


Want a message when I reply to your comment? Put your Twitter handle here.