5

You need to authenticate the connection to SharePoint using the FBA user's credentials. C#: ClientContext clientContext = new ClientContext("http://YourUrlHere"); clientContext.AuthenticationMode = ClientAuthenticationMode.FormsAuthentication; clientContext.FormsAuthenticationLoginInfo = new FormsAuthenticationLoginInfo("username", "password"); VB....


4

If you extend a WebApplication you have to have some difference in the url (could be http vs https) otherwise SharePoint has no way of knowing which zone you're in. But if you're using SharePoint 2010 then you don't need to extend to get the behaviour you want. If you enable both Windows and FBA in your zone the default Login Page provides a LogonSelector ...


4

After doing some research into this, I have a possible solution to determine ADFS authentication, but I have no way to test this. Here's the idea (point by point): 1) There is a class called System.Web.Security.SingleSignOn.SingleSignOnIdentity. SingleSignOnIdentity Class - MSDN 2) In Testing Whether ADFS User Is Authenticated they cast the user identity ...


4

Do I need to do any configuration at Central Administrator? If you want it just for your personal machine then you shouldn't touch CA. You need to perform some additional steps, e.g. creating a group policy and modifying IE Enhanced Security Configuration. Follow this article out, How do I make our SharePoint site stop asking me to login? – Part I How ...


4

Why create a custom login page when you can achieve this by breaking the inheritance permission on that document library. Break the inheritance permission on the document library and grant permission to only those users/groups that should have access to that library. Users/groups not granted access to this document library, will pop-up window asking for ...


4

You need to turn off Windows Auth on the Zone where you have Anonymous enabled. That will prevent users from attempting to authenticate to the site when browsing anonymously. This is done via Central Administration -> Manage Web Applications -> highlight the Web App, click on Authentication, find your Anonymous-enabled Zone, and then disable Windows Auth (or ...


3

I called Microsoft on this (case 11303​0110256288) and it's a product bug in 2013 - apparently a regression from 2010. Another customer had reported the same issue. It's an acknowledged bug with no KB yet. They hope to pick it up in an upcoming cumulative update but it wasn't know when to expect it yet.


3

@James Love got this on the head, you need to take a look at the cookies Check out this project "Remote authentication with claims" I believe the answer is here in the code. It requests the authorisation cookie from the target server if it get's it, it continues. That's your claims based right there.


3

Switching from claims to classic is possible (as @saumilm describes), but it's not supported and you have to recreate all permissions. In your comment to @saumilm you mention that you haven't created your webapp yet, wants to start with windows, but have to option to add forms later. In that case you're free to choose, forms is claims, so you can start with ...


3

Yes you can! You can switch your Authentication Provider between either Claims Based Authentication(CBA) or Classic Authentication, before embarking on changing the authentication provider I would first recommend reading the following technical articles: Migrate from classic-mode to claims-based authentication Plan Authentication Method More information ...


3

Was this windows account the same one with which SharePoint was installed? In that case, you could try to create a new user in AD and then login using the new user credentials.


3

You can use JSOM by javascript like two different ways: Using sp.js _spPageContextInfo.userLoginName Or you could use REST function getCurrentUser() { var endpointUrl = _spPageContextInfo.webServerRelativeUrl + '/_api/web/currentuser'; return $.ajax({ url: endpointUrl, method: "GET", contentType: "application/...


3

You most only have a single profile for any one individual. SharePoint sees the identity as two different users, and they cannot be 'merged' together. If you are unable to switch to a single provider for all Web Applications/users, you may want to look at one UPA Service Application per Web Application. To give you an example, you may have a user come ...


2

You probably have your default(internal) URL set as Trusted site (or Local Intranet) in IE settings, making IE to automatically login using your Windows credentials. Add external URL to Trusted sites or Local Intranet and you should no longer get login prompt.


2

Looks to me like there are some rogue configurations in your web.config. Did you ever set a custom membership/role provider manually or in IIS? Did you ever use FBA? The error message you're getting looks like there is a custom membership provider set which uses a non-existing (or no longer existing) connectionstring for a local SQL server instance. So when ...


2

if you can do something with User Interface then you can easily do that thing with Coding But building a Gadget the way you are trying is not really coding. Here is a tutorial on how to build a gadget using C#. Once you have that down you would then need to learn how to use the SharePoint web services. Then you would generate a proxy class from the list ...


2

As far as I know converting from Claims to classic isn't supported. I'd delete the old web application, BUT keep the content database. Create a new web app using the old content database. Assign new windows site collection admin and the re-create all permissions using windows accounts groups.


2

Check the permissions of the Report Library where the reports(.rdl) are uploaded. At times,report library will need contribute level access rights for all the users who wish to see the reports inside this library. Also it is advised that do not use inherited permissions on the report library. Stop inheriting permissions and give permissions directly on the ...


2

Enable FireFox Kerberos Trust Open FireFox In the Location bar, type about:config, and press enter. The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page. In the about:config page, search for the preference network.negotiate-auth.trusted-uris, and double-click ...


2

Kai I have done the solution but it's done the client in the Visual Studio 2012 using Service references. The solution is to make sure that you send a NTLM authentication request. Here is the complete source code for a console application being done in Visual Studio 2012: using System; using System.Collections.Generic; using System.Linq; using System.Text;...


2

Yes. I think you need to use an HTTP PUT to send the file to the server. Then, having sent it, you'll need to retrieve and set it's details using the client object model. To upload a file, you can use something like: WebRequest request = WebRequest.Create( "http://somedestination" + "/" + filename); ICredentials creds; //Set your credentials request....


2

how about following msdn? try using ClaimClientContext.GetAuthenticatedContext instead string targetSite = "http://SharePointServer/"; using (ClientContext CNX = ClaimClientContext.GetAuthenticatedContext(targetSite)) { //Load Libraries from SharePoint CNX.Load(CNX.Web.Lists); CNX.ExecuteQuery(); using (...


2

Finally got to the bottom of what was causing the issue, firstly would like to thank both @MdMazzotti and @Hugh Wood for their persistent help. In the end I stumbled on the fix which turned out to be partly because the way the site was built. In my particular case the site was built as a sub-site in SharePoint, for whatever reason this meant there was no ...


2

There are many ways to get logged in user name SPWeb site = SPControl.GetContextWeb(Context); SPUser user = site.CurrentUser; string strUserName = user.LoginName; or you can use SPWeb web = SPControl.GetContextWeb(this.Context); string userName = web.CurrentUser.LoginName; or you also can use string userName = this.Context.User.Identity.Name;


2

One approach could be to develop an HTTP module (a class implementing IHttpModule), declare it in web.config (could be with a WebConfigModifications used from inside a feature event receiver scoped WebApp). By subscribing to its AuthenticateRequest event you can run code after any request is done with autthentication.


2

Before doing the Custom login page for windows authentication, you have to configure your web application web.config file to authenticate current user credential against active directory. Here is a link which may help you on that. And Creating a Forms Based Authentication will be easy. You can get help from here on that. ADFS is not mandatory to these. But ...


2

There's different levels of permissions in SharePoint (names are mine, not official ones): Functionnal levels for contents: these are permissions you grant users from the sites (adding users/groups in roles, etc.), at the site collection level (define a user as a site collection Administrator) or even at the Web application scope (User Policy for the Web ...


2

Looks like you are working with Office 2016. It has Modern Authentication enabled by default. There is a Registry-Key EnableADAL - try to disable it on your client. But be aware, this will break lots of cool stuff with Office365. This is one of the many reasons why i do not like FBA: It's cheap, but has tons of drawbacks. Office-Integration is one of them. ...


1

Please make sure that your Build Configuration for your windows application is set to Platform Target: (Any CPU) or Platform Target (x64) in Project Properties --> Build --> General in Visual studio For setting permissions on ClientContext: CNX.Credentials = new NetworkCredential("user", "password", "domain"); or CNX.Credentials = ...


1

You can configure FBA on the same web application in SharePoint 2010 without having to extend it. (Your web application will need to be configured to use Claims-based authentication and not classic...I'm assuming that's already the case). There are numerous tutorials about the steps required to configure FBA, which generally boil down to: Creating the ASP....


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