Tag Info

Hot answers tagged

5

Instead of a network credential, you will need a SharePoint Online Credential: http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.client.sharepointonlinecredentials_members(v=office.15).aspx


4

The big difference with claims based authentication is that you can easily (well it is still SharePoint) add other providers. For example you can add another provider and being able to sign in with your google account, live-id, linkedin account etc etc. Claims-based identity allows you to factor out the authentication logic from individual applications. ...


4

In order to consume SharePoint REST service using .NET you could consider the following approaches: HttpClient - Provides a base class for sending HTTP requests and receiving HTTP responses from a resource identified by a URI. (.NET Framework 4.5) WebClient - provides common methods for sending data to and receiving data from a resource identified by a ...


3

If you maintain MySites in another web application you need to know that pictures are stored in a library User photos in My sites Host, reason for which everywhere where User picture needs to appear (e.g. comments, notes) it makes a separate request to the other Web Application. if the site loading pictures is itself anonymous, you would need to enable ...


2

Try this: var ctx = new SP.ClientContext(); var user = ctx.get_web().get_currentUser(); ctx.load(user); ctx.executeQueryAsync(function() { var loginName = user.get_loginName(); console.log(loginName); }); Now you shold be able to see the type in the loginName variable. I'm not 100% sure, but its worth a try. For example I get i:0#.w|somedomain\user ...


2

My first guess is, have you specified redirect url while registering your app in appregnew.aspx page? For more info check this link Basically what is happening is when you use bookmark to navigate to your app, the context token has expired. So you need to redirect to sharepoint site first to re-authenticate. Hope this helps.


2

If you are looking for SSO like scenario ,i think you can implement SAML . Pass the SAML token to Sharepoint(Relying party) , when users login to the third party application(Identity Provider) or click on some link on third party appliction to enter your SharePoint site.


2

You cannot configure the Forms based authentication if your web application is using Classic Mode Authentication


2

NTLM is not supported for SharePoint online. You have to use the OData API which requires OAuth authentication. Out of the box, SSIS will not support this and you will have to write CLR code if you are going to try.


2

OK, found it. The two parameters -AuthenticationProvider and -AuthenticationMethod are from different worlds, not to be used together. The first one works with claims based auth while the second one with Classic Windows auth. To achieve my goal I need to use these commands: $auth = New-SPAuthenticationProvider -DisableKerberos:$false New-SPWebApplication ...


2

How to delete SP.Group in SharePoint 2013 via JSOM Use SP.GroupCollection.remove, SP.GroupCollection.removeById or SP.GroupCollection.removeByLoginName methods to remove Group from site. Example var context = SP.ClientContext.get_current(); var groups = context.get_web().get_siteGroups(); groups.removeById(groupId); context.executeQueryAsync( ...


2

Keep me signed in uses cookies to keep a user signed in...so this is only an issue for users who share their computer with other users. In situations where users are sharing computers it should already be standard policy to log out of any sensitive apps and accounts that shouldn't be accessible to other users... I don't see any real security flaw here. ...


1

You should Create Different AD Account for your Contractors and Partners Different From all your FTE(Full Time Employees) lets call it All_Employees. Add All_Employees into your SharePoint Site which will give your FTE's Access to your site, but not Contractors . You should Contact your AD Vendor and Request this information from their's end to apply these. ...


1

To configure the Kerberos, you have to perform following steps. Configure SQL Server for kerberos Authentication Create DNS entry for your web application Create SPN for the DNS(you will use to access the SharePoint) Make Changes in Central admin and change authentication To Kerberos. Enable Constrained Delegation here is complete guide and step by step ...


1

In my opinion it is not a problem with the AAMs as you can access http://myserver.domain.com/pages/home.aspx and other pages of this site. It sounds to me as if the problem would be located on your root site. Just as a first step: Did you check if masterpage, style sheets, script files etc. are checked in and published? (although I think that at least ...


1

I would recommend JShare. It is Android and Java library for SharePoint. It supports few authentication options including NTLM.


1

Question # 1 Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013.Due to the widespread use of claim-based authentication for user authentication, server-to-server authentication, and app authentication, we recommend claims-based authentication for all web applications and zones of a SharePoint 2013 ...


1

You can use the Profile Provider for this, which let's you associate any arbitrary information you wish with the user. Alternatively, you could create your own table(s) that store additional user-related information. This is a little more work since you're on the hook for creating your own tables and creating the code to get and save data to and from these ...


1

If anyone ever has the same problem, I found a solution to this: instead of hardcoding the wreply parameter, I first access the SharePoint site + "/_forms/default.aspx" with a request that does not follow redirects and has the user agent set. The response has a Location header that I get and which contains a wreply parameter. Only the left part (in the Uri ...


1

First of all, a user must be a site collection administrator to be able to grant an app to use app-only policy. Once you have installed and trusted (granted) an app, you can use app only requests to the site or web. Basically there is an accessToken called App Only Token that you have to create in your code to request app only access. Here is the sample ...


1

FEDAuth cookie is essentially just a pointer. It tells SharePoint how to validate your credentials from the secure store service. It's probably much more trouble than it's worth to try and re-use that scheme as is. You could use ADFS or write a simple custom STS that can give you a custom token that both your service and SharePoint can accept. If you ...


1

ADFS: The TokenLifetime property can be set at the ADFS end using the command upon creation . Below is example is for 2 sec . Set this value to a high number ,so that the session never expires while working on page . Add-ADFSRelyingPartyTrust -Name "abc" -Identifier "https://abc/_trust/" -WsFedEndpoint "https://abc/_trust/" -TokenLifetime 2 ...


1

Use claims based authentication for web application and have your client send SAML tokens . The client(Identity Provider) can send you (email,role claims) and Sharepoint (Service Provider) can trust them .After establishing the trust , add the users to sharepoint group so the user can access your site. By using SAML the SSO requirement is also satisfied.


1

When you are configuring a BCS connection via SharePoint Designer you get 3 options, one of which is "Connect with impersonated custom identity." This option allows you to create a SQL Server or other account type (i.e. not a Windows AD account) and store those credentials in the Secure Store Service Application. The Secure Store keeps these credentials in a ...


1

To set up you SharePoint application page to allow anonymous access, the key here is that you cannot use the default LayoutsPageBase base class for your page because it would trigger SharePoint to prompt anonymous users to log on. Instead, you need to use another base class for your anonymous application page called UnsecuredLayoutsPageBase. You can find ...


1

After converting our 2010 farm to use Claims based authentication, out ArcGIS web services stopped working and our custom WCF web services no longer got the user credentials - I believe they function with anonymous access. It turns out that WCF web services need to be Claims Aware, which they are not. WCF Services used by Silverlight inside of SharePoint are ...


1

What I believe is the major difference is that with classic mode, you login directly, and if you need to be authenticated to a second server, it's not possible (you need to be logged in to this second server first -> new login screen). You will find that this is still often done but in that case the second connection is done under a different account (with ...


1

You could try to close the tab/window with Javascript in your SignOut.aspx page using window.close(); SP 2013 already does it like this (bad formatting included): <asp:content contentplaceholderid="PlaceHolderAdditionalPageHead" runat="server"> <SharePoint:ScriptBlock runat="server"> function _spBodyOnLoad() { window.close(); } ...


1

we can have the user login with their Office 365 credentials No, until user hand them to you himself. then get their original office 365 domain (xxxx.sharepoint.com) returned or something similar? Create a remote event receiver, so when an app is installed, it will return with host web URL, which can be done using an hidden app part (maybe) or ...


1

Few things that you should see: Make sure the default page is checked-in and approved (if its checked-out or pending for approval, it won't be available to anonymous users) Make sure all items in Style Library/Site Assets are checked-in and all these libraries have Anonymous Access (sometimes Style Library/Site Assets are not inheriting permissions from ...



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