Tag Info

Hot answers tagged

7

Have you considered using Tenants? http://www.harbar.net/articles/sp2010mt1.aspx http://blogs.msdn.com/b/russmax/archive/2010/04/02/sharepoint-2010-multi-tenant-hosting-part-1.aspx http://blogs.msdn.com/b/russmax/archive/2010/04/03/sharepoint-2010-multi-tenant-hosting-part-2-configuring.aspx EDIT: As usual when we are talking SharePoint best practices, ...


6

The key question is: Are the users authenticated in any way? If the answer is 'no', then you are OK because SPF requires no user license. If 'yes', then keep reading. I am not a licensing expert, but here’s what I've been able to piece together: SharePoint Foundation requires no additional licenses (CALs or External Connector), only what is required by ...


5

The site will feature regular logon (forms) For this I would recommend to use the Forms base or windows authentication The site will contain some lists where the content is either retrieved from local database or backoffice system OOTB SharePoint Lists can be use to save and retrieve the data (local i.e. saved in SharePoint ContentDB) while ...


5

You may extend the SharePoint Web application with FBA, to create an extranet-facing access point to provide access to the partners. Extending an existing SharePoint Web application provides a separate IIS Web site and you can group external users into a different security domain than internal users. This approach makes it easier to manage different ...


4

In SharePoint 2010 you can actually have dual authentication methods on a site when you use Claims Based authentication. This link should help you get FBA set on on 2010. http://blogs.technet.com/b/speschka/archive/2009/11/05/configuring-forms-based-authentication-in-sharepoint-2010.aspx


4

Please take a look at TMG formerly ISA. You will need to provide the ability for the external users to register etc. Take a look at SharePoint External Collaboration Manager very inexpensive product by SharePoint solutions (I don't work for them). It takes care of New User Registration, Forgot Password etc. You might want to create 2 different zones of the ...


4

We have had an extranet built on SharePoint since 2006 and we made the initial decision to put each client into their own site collection. I know that's a lot of site collections and for us, since we put each site collection in it's on databases, it's a lot of databases. But we feel like that decision was the correct one. It also leaves the most ...


4

Here is detailed guidance on licensing SharePoint products: http://sharepoint.microsoft.com/en-us/buy/Pages/Licensing-Details.aspx For internal users they must have a valid windows server license. In most scenarios this is true for all users otherwise you are not allowed to connect to any windows server box (fileshare, ...). Thats why SharePoint Foundation ...


4

This is typical of a SharePoint implementation. If you think of SharePoint more as a platform than just an application, customization is expected and desired. Whether you proceed with SharePoint as your platform or choose another platform most likely will depend on the resources you can secure to implement this. As SharePoint customization help is in ...


3

UAG is not going to "re-architect" the way SharePoint works. UAG will provide you with an added level for Defense in Depth, by forcing authentication prior to hitting SharePoint, as well as allowing you to NOT have your SharePoint servers directly to the internet via reverse proxy. You still need to define your security boundaries inside SharePoint per ...


3

All of the responses previous to mine are good, but another (so far unmentioned) option is to utilize a separate AD for your external environment. I previously worked on a large-scale global environment that was configured this way. Granted, it was more than just SharePoint, our external AD was used for all non-badged users including contractors, vendors, ...


3

I've planned something similar, that we are testing now. We have SP deployed in its own network space with dedicated AD deployment with a one way trust back to the production AD. External users are added to the SharePoint AD while internal users are authenticated via production AD. With this setup you only need one authentication provider, you can use ...


3

If you run your farm on least privilege settings, you can get the above error. Be aware of the security demand for the Word Viewing Service are quite high: When you create a new application pool, you can specify a security account that is used by the application pool to be either a predefined Network Service account or a managed account. The account ...


3

We made the mistake of putting everything into a single site collection for one type of external program we run. The biggest problem we found was that when doing a security review, it was more difficult to assess where security inheritance was in place and where it was broken. As these types of extranet are ongoing, it's easier to just deal with the problem ...


3

Definitely don't put everything in a single site collection, and if you really want people not to even know the other users and sites exist, you'll probably want to look in to the peoplepicker-onlysearchwithinsitecollection property. A lot of the other options depend on where you want to store your users (i.e. using Windows auth, FBA, etc). It's hard to ...


3

You can expose your SharePoint WFE on your DMZ and rely on Form Based Authentication (or any other claim based authentication provider) (or even assume they have an account in your AD and connect through NTLM although you might have issue with proxies) but that's risky (but working) If you have ForeFront / ISA / F5 / ... you can expose some of your ...


2

You might also try using Microsoft Forefront Unified Access Gateway for it's advanced authentication schemes. Using UAG you can set up a form that authenticates a user to their windows account on the extranet access, while continuing to use the regular windows account on the intranet. Reference: Why enable SharePoint extranet access with Forefront UAG?, ...


2

You can mix authentication providers within a single SharePoint Web application. You could use Windows authentication for your intranet users and claims-based or forms-based authentication for your external users. Here's a resource that describes claims-based authentication for SharePoint 2010: ...


2

We usually go with separate site collections in cases like this also. If the site is on SharePoint Foundation, you would not be able to search across site collections, right? I would think that is a nice added security feature in this case as well. You could always have one site collection that is accessible by all customers for common content, then link ...


2

Is it "typical"? Yes. This task are pretty common for developing SP stuff. Do you have to "roll-our-own"? Depends on the the requirments but in "difficult" cases almost always yes. Is this a correct questions? No. You have to determine the problem otherwise it will be closed UPD: Logon (forms) - Default exists. but most likely you will need custom ...


2

I would say that for these requirements SharePoint is bit overkill. If you have deep understanding how SharePoint works then go for it. If no, custom app written in ASP.NET will be developed faster than trying to figure out how to work with SharePoint.


2

It sounds as though you understand the concept of Web app extension so there isn't too much I can add really. Something that hasn't been mentioned is the fact that extension creates an additional IIS site. You may wish to configure this site in a different manner to the original, e.g. configure an SSL certificate for access over the Internet or change ...


2

Check with Configure an Alternate Access Mapping in SharePoint 2010. http://technet.microsoft.com/en-us/sharepoint/ff679917.aspx


2

for that scenario you have two options: First option: SharePoint trusting LiveID and ADFS Second option: SharePoint trusting Windows Azure Access Control Service (ACS) and ACS trusting LiveID or ADFS. First option Configure claims-based authentication using Windows Live ID (SharePoint Server 2010) Configure authentication using a SAML security token ...


2

Thought it wouldn't be advisable to have multiple people using the same login, there isn't any limits specifically to the number of concurrent connections per username. For capacity planning, treat each individual connection as unique when determining the number of users you need to support. So, if 3000 people are using the same account, plan for 3000 ...


2

this is very easy: Extend it : this article and this but if you can learn how to configure it like professionals, do these steps: 1- design you can design it in multi layer : firewall - DNS - Router - ... 2- configure it for higher security with firewall or ISA Server or other solutions : this article 3- access the site by grant permission to your ...


1

I am pretty sure this is still a matter of getting the alternate access mappings correct. Unfortunately, I am not great shakes at this. Try reading through this blog post. You may want to try a mapping from Internal Url http://[ip.address] to Public Url http://[Public URl]. This stackoverflow question will help determine which zone you want.


1

All three options you list will work fine against multiple farms. As much as possible I'd stick with CSOM or REST. And as you want to work with both Documents and List items the CSOM is probably the best choice.


1

It would be handy if you could share the format of the URLs with us, as well as let us know whether the sites are located in separate Web applications. It's likely the the links work fine for internal users because they are domain joined and their Web browsers consider the sites to be in the local intranet (e.g. if the domain is called "company.com" and ...


1

Foundation will meet all your requirements except for the profile information piece. That would require Server or Enterprise but you can find quite a few articles on creating your own profile service. Pros Can easily be branded Use Business Connectivity Services to get back office data Can use forms authentication and create your own groups More ...



Only top voted, non community-wiki answers of a minimum length are eligible