I want to create the sharepoint 2010 site on SahrePoint 2010 server. I want to make it available in intranet as well as internet. what exactly i need to do ? is i need to configure mix mode authentication ? how ?
Look at Alternate Access Mappings:
How Do I: Configure an Alternate Access Mapping in SharePoint 2010?
Server Name Mapping and Alternate Access Mapping (AAM)
Making a SharePoint 2010 site externally available
Regarding authentication, you can use Classic Mode Authentication for externally available sites, but all users will need an Active Directory account. Otherwise, you might want to use a web application with Claims Based Authentication that uses a mix of Windows Authentication and Forms Based Authentication.
Note that externally available sites that require authentication are technically extranet sites. An internet site usually means that anonymous access is allowed (at least in part). In the case of SharePoint internet sites, special licensing might be required.
Related
There is Sharepoint 2010 intranet portal with several intranet sites based on Active directory user access. Is it possible to create one more site with quite different security model for Internet access or should I create standalone portal for Internet users? What shall I consider?
You can have different authentication models at "Web Application" level. This means that all your site collections inside your Web Application will work with the same authentication model.
If you already have a web application working with Active Directory and you want to provide Internet Access (probably using Forms Authentication) you will need to create a separate Web Application.
Here is a sample Video on how to create a new Web Application:
http://www.youtube.com/watch?v=0Z8vb42j1wQ
And this is a video on how to implement Forms Authentication a Web Application:
http://www.youtube.com/watch?v=yBqL3E-ne60
I am new to windows azure development.
I am developing an application for hosting online tests.
This application needs to have multiple authentication options like Windows live ID, Facebook etc.
It also needs to have default form based authentication fed by the database in back end (simple User name and Password match).
Based on the authentication mechanism different permissions will be available to the user.
Can anyone please suggest how i should proceed on this?
Thanks
Do you really need forms authentication, or do you just need an application specific store where people can use a credential specific to your app?
I'd suggest researching Windows Azure Active Directory and Windows Azure Access Control Services together. You may create either an AD tenant for your application store and use it as an Identity Provider for ACS or you could host your own Secure Token Service and Identity Provider which uses your backend database as the user store also registered with ACS. This means that all of your authentication goes through the same process and allows for you to have your own user store, plus the social Identity Provider capability.
The key here is that you want try to avoid having forms authentication AND Social, but rather a mechanism where multiple Identity Providers can be used, including one of your own.
As Gaurav stated there are a ton of resources out there for this:
Understand the difference between WAAD and ACS.
Provisioning an Azure AD Tenant as a Identity Provider in ACS
Windows Azure Identity
There are also many blogs and MSDN documents talking about how to set these up.
If you start with the default "ASP.net MVC4 Web Application" template in Visual Studio you get a web application mini-sample with an AccountController that supports local and 'social' accounts out of the box. See documentation here. It is based on DotNetOpenAuth (a fantastic lib with terrible documentation) and a Microsoft implementation of an special MembershipProvider which lives in WebMatrix.WebData.
Regarding the Azure Access Control Service 2.0: I have no idea what the status of this service is but it looks to me as if MS itself tries to discourage developers form using this service since it was to deeply hidden somewhere under Windows Azure Active Directory in the documentation.
we have a sharepoint 2010 site and are using the same url to access it from inside and outside the network.
our issue is that we don't want users inside our network to get asked for credentials when accessing the site.
if, for example, the url we wanted to use was https://sp.domain.com, how would we set this up?
You can do this via Alternate Access mappings. Have two zones for your sharepoint site: Intranet and Extranet. In AAM settings:
Intranet : http://sp.domain.com
Extranet: http://extranet.domain.com
You did not specify which authentication scheme if you are using for outside network. If its forms authentication, you can set Windows for 1 and Forms authentication for 2.
However, if its AD only for both, you will have to have sp.domain.com configured as Intranet Url and extranet.domain.com as Internet Url in each of client computer. This can be done using group policy.
Your proxy server will have to do the work of transferring the sp.domain.com from external network to extranet.domain.com internally.
Good to read:
http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=804
I need to implement a web application hosted on sharepoint. This is a client requirement. So I cannot create a standard asp.net web application. Another client requirement is that the authentication is not an active directory one but they want to use an existing database of users.
I am a bit concerned how this would work on sharepoint because users would need to log-in onto sharepoint. Would it make sense that users log into sharepoint as anonymous and then we use our custom controls for log-in. How does sharepoint handle anonymous users?
Any assistance would be greatly appreciated
When building apps over SharePoint, you use the SharePoint authentication mechanism, whatever it is.
Does the SharePoint farm is already in place ? Or do you have to also build the farm ?
In the former case, probably the authentication mechanism is already in place and you just have to build a "standard" sharepoint application.
In the later case, you will have to carefully plan your authentication. SharePoint can use a combination of AD authentication, Forms authentication (over a DB in your case if you want) or a Claims authentication pattern. My guess is that a Forms authentication with a custom Membership/role provider is the way to go.
I was just wondering how do I make a sharepoint 2010 internal site that I already have an external one, meaning it can be accessed anywhere where you have access to the internet.
Thank you in advance.
Apart from licensing issues, I think you'll have to
enable anonymous access (in central admin and at the site collection level)
use a publicly accessible domain name