Tag Info

Hot answers tagged

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

To use the Outlook Web Access web parts such as MyInbox, MyTasks and MyCalendar requires authentication to the data inside of Exchange. If you want it to work automatically, then you need to have the SharePoint web application setup with Kerberos. This allows the user's credential passed to SharePoint to be forwarded (delegated) to another system. This ...


4

Lots of ambiguous words in the SharePoint auth landscape.... There are two Authentication Methods: Classic Mode and Claims Mode. Classic Mode supports Windows NT authentication. Claims Mode supports Windows NT, Forms-Based and SAML 1.1/WS-Fed authentication. To see what is being used, you need to look at the "Edit Authentication" page in Central ...


4

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"); ...


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 ...


3

It is the Application Pool Identity. For more information, see http://technet.microsoft.com/en-us/library/cc678863.aspx SharePoint takes care of providing appropriate permissions for this account.


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

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

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

@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

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.


2

No, that's NTLM authentication.


2

The plumbing to handle anonymous/unauthenticated users already exists within SharePoint...you don't need to re-create it by logging them in to what in affect would be another anonymous (...guest) account. If you're going to log anonymous users in to let them access the site then just enable anonymous access and go thru and grant them access to the pages, ...


2

You're on the right track. Yes, both TMG and UAG can be used to publish out SharePoint in the manner you need. The choice between which product to use depends on which feature set you need. Microsoft's Extranet Topologies diagram (PDF) compares ISA, TMG, and UAG (for Visio or XPS versions of this document, see the SharePoint 2010 Technical Diagrams page). ...


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

You'd have to turn on impersonate in the webapp. This way requests done to underlying systems are done using the currently logged in user's identity. This works on local machines only though and is thread specific. To send the current user's identity to other systems, delegation is also required: ASP.NET Impersonation & Delegation ...


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 ...


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

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 ...


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 ...


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

Wictor Wilén has written an excellent guide for authenticating to Office 365 from Client object model here. But he, and everybody else, uses FedAuth with a username / password combination. This is due to the fact that this is how most configurations are set up. Microsoft has released this guide for doing Remote Authentication (Claims based!) via the Server ...


1

I answered a similar question recently. SharePoint 2010 you should use the Secure Store Service (SSS) for these kind of settings (credentials, connectionstrings etc). That provides a user interface for selected users, you can then in your Web Part Property point to the SSS application ID that you want it to use (you could also get fancy and make the ...


1

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 ...


1

When you want to use custom host headers with windows authentication, you have to disable loopback check or whitelist the host names. Follow this Microsoft KB. I highly advise you to use the second method (white list) on production servers, as the first method shut down a security mechanism.


1

Typically, when you have the need to access content both as Anonymous/Forms and Windows, you usually have to extend the web application to a new port\hostheader combination and enable Windows Authentication on that. Both web applications still point to the same data so there are no synchronization issues. Here is a short explanation of the approach


1

There is a command in PowerShell under a SPWeb object called MigrateUsers. But tbh im not sure if it works the other way, setting it true converts users from classic to claims. One should think setting to false would do the opposite. But I haven't tested it. Using the Move-SPUser command with a powershell script should do the trick. Something like this



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