Tag Info

Hot answers tagged

5

The domain that needs to be isolated is only a DNS domain not a new AD domain. This is purely such that you have a separate IIS site where Cross Site Scripting is prevented by the browser. You can add that new domain in DNS (see Configure an environment for apps for SharePoint (SharePoint 2013)) or hosts file. The High trust app still needs the same ...


4

You should use SharePointOnlineCredentials that handles all the handshaking, claims and oauth in SharePoint online. using (ClientContext clientContext = new ClientContext("https://innergen.sharepoint.com/sites/mydevsite")) { SecureString passWord = new SecureString(); foreach (char c in "yourpassword".ToCharArray()) passWord.AppendChar(c); ...


4

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


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


3

It would be best to handle this at the IIS level with two-factor authentication. You could write custom code in SharePoint to try to accomplish this, but trying to write your own security layers is usually a bad idea. Microsoft offers the Windows Azure Multi-Factor Authentication service that might work for you: ...


2

FedAuth Cookie is what is used with Claims Authentication. SharePoint STS will issue the FedAuth Cookie which contains the references to the claims token. Claim tokens are actually stored separately. I believe the ASPXAuth cookie stores the actual user (as SharePoint recognizes them) and whether they are currently authenticated. They work together, and ...


2

I presume you mean a SharePoint 2010 forms authentication site where userid and password are to be provided. Check the code snippet below - you'll have to check exception value below and handle the exception accordingly (cancel login, etc). See the FormsAuthenticationLoginInfo class for more info. try { ClientContext fooCtx = new ...


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

to use javascript you need to send a post request to a webservice, the url should look like this: /_vti_bin/authentication.asmx to read up on javascript post event read up here: http://api.jquery.com/jQuery.post/ the syntax is: $.ajax({ type: "POST", url: url, data: data, success: success, dataType: dataType}); so from the above ...


2

A quick Bing search shows a few options. http://sharepoint-live-authentication.shetabtech.com/ - Paid option http://openidmembership.codeplex.com/ - free option http://blogs.perficient.com/microsoft/2011/01/updated-adding-an-openid-claims-provider-for-ad-fs-2-0-to-extend-access-to-sharepoint-2010/ - a how-to


2

If you can add users to the FBA Pack, but you can't login, that means that your SharePoint web application web.config/machine.config membership settings are good, but your SecurityTokenService web.config settings are not. Check your SecurityTokenService web.config membership settings and compare them to your web application web.config/machine.config ...


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

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


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.


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

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


1

This means you have some asset you have not checked in, published and approved. It could be an image, css file or master page you are using.


1

You can interact with SharePoint content remotely with the Client-Side Object Model (CSOM). To get started, see http://msdn.microsoft.com/en-us/library/ff798388.aspx. EDIT: You can also use the REST api: http://msdn.microsoft.com/en-us/library/ff798339.aspx


1

This will help you: 2D00-Plain-and-Simple_2100_.aspx">http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2014/01/22/Office-and-SharePoint-App-Model-Authentication-2D00-Plain-and-Simple_2100_.aspx


1

Server-server authentication allows to access and request resources from one server on behalf of users. Server –server authentication will be possible in SharePoint 2013, Exchange Server 2013, Lync Server 2013 and others that support Microsoft server-server protocol. Server-server authentication is separate from user authentication and it is not ...


1

You can pass credentials as follows: ClientContext clientContext = new ClientContext(siteUrl); clientContext.Credentials = new NetworkCredential("Login id", "Password", "Domain");


1

To use Outlook Web App Web Parts, you must, at a minimum, be delegated "Reviewer" access to the content that you're opening. If you've embedded an Outlook Web App Web Part that requires authentication into an application, you must pass authentication information through together with the request for the Web Part. One way to do this is by ...


1

You can create a custom Trusted Identity Provider (STS, security token service) with your own membership inside. Few links to dig deeper: http://blogs.msdn.com/b/life_of_a_sharepoint_consultant/archive/2010/12/01/writing-your-own-trusted-identity-provider-for-sp2010-1.aspx http://msdn.microsoft.com/en-us/library/ff955607%28v=office.14%29.aspx


1

If you have an issue with the Secure store, it might be wise to re-create the application definition. Your scenario, if I got it right, should enable a pass-through SQL connection to all users by using a single SQL Account. In such situation you need to verify that the Secure Store application is properly configured: Create it for a Group in the "Target ...


1

An approach to authenticate to SharePoint online using JQuery http://code.msdn.microsoft.com/SharePoint-Online-d9fdb136


1

I had implemented FBA and done this two part blog on my site. Please have a look at the steps I have followed and verify that you are't missing anything. Below given are the links to my blogs that explains FBA implementation. First blog describes how to create Membership Provider and role provider and prepare the DB. Second blog describes how to make ...


1

include domain if necessary $username = "username" $password = "password" $cred = New-Object System.Management.Automation.PSCredential -ArgumentList @($username,(ConvertTo-SecureString -String $password -AsPlainText -Force)) assign $cred to the webServicesProxy.Credentials $webServicesProxy.Credentials = $cred


1

Ok, so I fixed this by adding additional SPNs for that server by not specifying the port. If anyone else faces this problem, it is documented in the Microsoft documentation on how to setup Kerberos for SharePoint. It is a bug that SPN tickets are not correctly formed for Non default Ports. So the answer, is to add a SPN without a port number for those ...


1

After reading that IE automatically puts a URL into the internet zone when it includes a period (.), which forces the browser to ask for credentials, I created a new DNS record - a Host (A host this time), with name 'portaldev' pointing to my IP 12.3.4.567. I added the new binding to IIS and in Alternate Access Mappings added an internal URL pointing to the ...


1

Migration of SP2010 web app from Classic to Claims: 1) It is irreversible process as mention in Microsoft site. But its not correct. You need to do some extra work to revert back.Check it out here Sharepoint egg 2) There is no support for conversation from SP UI, you can do it either powershell or programmatically. 3) There are few steps for converting ...



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