I have created an authetication provider and went to central administration >> Authentication Providers and changed the authentication settings to Forms and filled in Membership provider and Role manager details.
Now, when i go to create a site collection under the above mentioned web application, the people picker in the create site collection page still refers to the active directory(central admin has windows authentication).
Can any one explain this behaviour?
I actually expected the People picker in the Create site collection page to refer to the Forms database rather than active directory.
Thanks
In the web.config for your web app, you need to change the value in the <PeoplePickerWildcards> node. Change the key to your membership provider.
You need to add your the configuration information for the membership provider to the web.config file for Central Administration. This will allow Central Admin to find from both AD and your own membership. There are examples on Technet for a SQL Server and an LDAP membership provider. Note how it mentions that the membership provider info needs to be added to both the web app's web.config and to Central Admin's. If you're using a Role Manager though, don't put that info in the Central Admin web.config, or at least not unless you really know what you're doing and why. :)
Once you do this the people picker should be able to find people from your FBA solution's membership provider. One little caveat if you happen to be using the same AD store (or some kind of replica) for both Windows auth and LDAP auth. You'll need to use the "prefix" of your membership provider name when specifying the user, otherwise the people picker will always lookup the native AD version of that user. For example, looking up "jdoe" will always find "domain\jdoe" first. If you want jdoe from an LDAP provider pointing at that AD, you'll have to explicitly put in "ldap:jdoe" (substituting whatever you called your membership provider in the web.config for "ldap"
Related
I want use Mixed mode authentication in my application.
I want Windows AD Authentication for intranet users and Forms authentication for internet users.
How can I configure this.
Check out the Kentico documentation for Mixed Mode Authentication.
Essentially you will:
determine if you want to import AD roles or not (web.config key)
Add an LDAP connection string to your web.config
Modify the membership and roleManager elements under congfiguration/system.web section in your web.config to use the AD connection string and provider
map the username field
It's not a hard setup really and much easier if you don't have users already in the Kentico system. If the username already exists in Kentico, the user will NOT be imported into Kentico from AD.
We have configured Okta as a trusted authentication provider to out SharePoint 2013 On-Premises environment. The user can log into Okta and access the SharePoint 'app' but when it connects them to the homepage, they are met with 'Sorry this site has not been shared with you'. It's like their account does not have access to SP, or is not being recognised. I can see in the logs that a valid SAML token is coming in, but I think we might be missing a step where that is converted to a valid Active Directory account.
In the deployment guide they talk about 'recommending' that we install the Okta People Picker plugin. I don't want to do this if we don't have to, I was under the impression we didn't need to add 'Okta' users into SharePoint as it would map the SAML claim to their Active Directory account and grant them the same access they would have if they were inside the network...
Any help would be appreciated.
First off, in order for users to be able to be looked up you'll need to definitely add the people picker plugin in. The biggest snag that the documentation doesn't accurately describe is that you'll need to import the okta cert chain to the server and establish trust in central admin for 2013 (not just 2010 only). Following all steps in the guide (including certs) got that going.
Okta-SharePoint on-prem guide: https://support.okta.com/help/articles/Knowledge_Article/Microsoft-SharePoint-On-Premises-Deployment-Guide
As for access to the site: once you get the people picker configured then you need to ensure you have migrated your user profile users from AD as the new type of claim for your identity provider. For the most part you can follow the guide below and just update the appropriate spots for Okta:
https://blogs.msdn.microsoft.com/sambetts/2014/09/03/how-to-migrate-sharepoint-users-to-adfs/
For extended troubleshooting I would recommend leveraging a ULS log viewing tool and to filter the results by the name of your claim identity provider.
I want to set up a website on Azure according to the following requirements and are wondering if it is even possible?
As a internal team member, I must be able to login to the site with Windows Authentication
As a external customer, I must be able to login to the site with user name and password
As a external customer, I must not be able to access a subset of the site
As a unauthorized user, I must not be able to access anything on the site
I guess I have to set up a VPN connection between Azure and the Active Directory in my company. How do I do that?
Is it at all possible to meet my requirements?
Background Information
We are a small project with about 10 team members.
We have four large customers who need access to the site, and there are a few people in each customer who needs to have access to the site.
Customers will just have read only access to static, non-sensitive information.
The team members will have write access, and will also handle some sensitive information.
** Edit **
I have now managed to create efficient synchronization of our projects local AD to Azure, thanks user18044. Unfortunately, the accounts for the team members is located in the company's AD (corp.mycompany.com), and out AD has one-way trust with it.
We have groups in the project-AD pointing to our accounts in the company's AD, but the members in the groups is not synchronizing over to Azure.
Can this be solved?
Yes, I think what you are describing is doable.
Your first two bullet points are about authentication. As Azure Active Directory does not directly support Windows Authentication, federation is the way to go here.
When you as an internal team member log on, you land on what is called a home-realm discovery page, where you pick the realm you want to authenticate in. Picking the realm of your company, you get redirected to the STS (for example ADFS) your company has set up to authenticate you. If you are in the same Windows Active Directory network as the STS is authenticating against, you should be able to use Kerberos to be issued a token.
An external customer would be redirected to another STS that would use forms authentication against a credential store to issue security tokens.
Both security tokens are then posted back to Azure Active Directory which is configured to trust both STS's and issues a token of its own. See here for an example.
As for the second two bullets, the authorization part you can do based on roles you assign to your users. Depending on which STS authenticated your user, you assign them a certain role. Based on that role you can give access to certain parts of your website or not. How to implement this depends on what stack you are using for your web application, but a Google search should give you some leads.
I have sharepoint 2010 application that has default zone and an extended internet zone. The application uses classic mode authentication. I want to convert the application to use claims based authentication. I followed this article http://bit.ly/9StUpd and http://technet.microsoft.com/en-us/library/gg251985.aspx to create a sample application and it works fine.
I have configured default zone to use windows auth and the extended zone to use Forms based authentication. I have only modified the web.config of extended application to use the connection string and membership provider settings as mentioned in the article.
Now my question is do I need to configure web.config of Default zone to use the asp.net membership provider settings.
I'm not able to search asp.net membership provider users in the people picker. The reason is I want to assign a user in asp.net sql membership provider database as site collection administrator so that they have access to all the site menu items.
I've imported a bunch of users into my Active Directory with some custom fields. Then I did a profile import from Active Directory to Sharepoint with all the custom fields and regular fields. After this, I needed each user to be in a site collection with a MySite set up for them. I did that by writing some code that ensured the user existed and then checked the profile attribute "personalspace" to see if a MySite had been created. Everything worked great until some of the users needed to login from outside the network.
I'd like to get rid of the windows authentication pop-up that a user would get if they hit from outside the network (or haven't added the site to their trusted zone in IE). I've extended my web application to create an internet zone. Then I edited the web.config of the internet site to do active directory forms authentication, along with editing the Central Administrator's web.config so that it can see the data source. This is all well and good, the user can login through a nice interface. The only problem is that now the user is detached from their user profile. Essentially Sharepoint views a windows authentication user and a forms authenticated user as two separate users.
Is there a way to link the profiles? Do I have to write a custom membership provider to log a user in and then link them up to their windows account? Is there a way to log a user in from the internet web app and then spoof their windows credentials and pass it to the intranet? Do I need to recreate all the user profiles based on the forms authentication data source?
Is this what are you looking for .. http://grounding.co.za/blogs/brett/archive/2008/01/09/setting-up-dual-authentication-on-windows-sharepoint-services-3-0-forms-and-ntlm.aspx ?
See ya
I've been trying to accomplish the same thing, with exactly the same problem - the "forms-authenticated-me" is not the same as the "windows-authenticated-me" to sharepoint, and I can't see how to map the two.
After a lot of frustrating efforts, I think I've finally realized it's not possible. In retrospect, this isn't too surprising.
here's an excerpt from http://msdn.microsoft.com/en-us/library/bb975136.aspx (my emphasis added)...
Deciding to Use Forms Authentication
Some organizations want to use Windows
users and groups in SharePoint
Products and Technologies, but enter
credentials via forms authentication.
Before using forms authentication,
determine why to use forms
authentication in the first place:
What is the business driver? If user
accounts are stored in a location
other than an Active Directory domain
controller, or if Active Directory is
not available in a particular
environment, using forms
authentication with a membership
provider is a good choice. But if you
want to force logon only via forms
authentication, but still use Windows
and all of the integrated features it
provides, you should consider an
alternative such as publishing the
SharePoint site with Microsoft
Internet Security and Acceleration
(ISA) Server 2006. ISA Server 2006
allows users to log on by using a
forms authentication Web form, but
treats them like Windows users after
authentication. This implementation
provides a more consistent and
compelling experience for end users.
You can set up the Forms Authentication to use the Active Directory Forms Authentication provider. You'll get the best of both worlds.
The login prompt will be the Forms Authentication prompt that you want, but the profile and login info will come from Active Directory.
Follow these instructions to configure the provider:
How To: Use Forms Authentication with Active Directory