Tag Info

Hot answers tagged

2

search cookieHandler in web.config of your webapplication, then add the persistentSessionLifetime property: <cookieHandler mode="Custom" path="/" persistentSessionLifetime="1.0:0:0"> http://msdn.microsoft.com/en-us/library/microsoft.identitymodel.web.configuration.cookiehandlerelement.persistentsessionlifetime.aspx it seams the property just ...


2

SharePoint does not perform authentication. What you are trying to do is not possible. The page you reference is for configuring SharePoint web applications. Microsoft's single sign-on approach is based on ADFS2.0. I recommend you deploy ADFS and configure SharePoint and your other application to both delegate authentication to it.


2

I believe that SP2010 and SP2013 both support/utilize WIF (Windows Identity Foundation) for claims-based authentication. (semi) Recently, there was a WIF extension released to support the SAML 2.0 protocol. http://blogs.msdn.com/b/card/archive/2011/05/16/announcing-the-wif-extension-for-saml-2-0-protocol-community-technology-preview.aspx With some ...


2

I am thinking why wouldn't you use ListData.svc instead of Lists.asmx to get the list data. ListData.svc provides a way of getting information from a list (or lists using joins) using REST and you end up with is a nice RSS feed of list data, that you can consume with whatever client you would like. Also, you don't have to create the Web reference as you ...


2

You can download this document Best practices for using fine-grained permissions (SharePoint Products and Technologies): http://www.microsoft.com/en-us/download/details.aspx?id=9030 T.s


2

The simple answer is you can't (Or it isn't designed so you can) get the token from your php you need to generate it from the app. Take a look at the tips and tricks page for more information: http://msdn.microsoft.com/en-us/library/fp179932%28v=office.15%29#Tokens and also high trust http://msdn.microsoft.com/en-us/library/fp179932%28v=office.15%29#S2S


2

I ran into this problem. It turns out that our corporate standard IIS installation made changes to the .NET configuration that conflicted with SharePoint. Basically, SharePoint's web.config files include a "windowsAuthentication" configuration. That was locked by the applicationHost.config file that disallows that. Edit ...


2

ACS won't give you back the Windows Live email. It's been always like that :( Here is a workaround using the Live API and some custom code http://nearbaseline.com/blog/2013/03/sharepoint-and-windows-live-id/ You can also try Auth0 which has SharePoint 2010 and 2013 support. It supports Windows Live giving back the email and many other providers. ...


2

this could be faulting at several stages! first place to look even tho you migh of already is look at the app pool, start or recyle "sharepoint webservices root". now go under sites and start "SharePoint Web Services" right click, manage and then click start or recycle. now do an iisreset. if that doesnt work, you could test this one out! Moving one ...


1

This problem indicates that the secure token service application is not functioning correctly. Following could be the possible causes of this problem (see http://support.microsoft.com/kb/2493524): A required WCF hotfix has not been installed on the SharePoint server Authentication for the SecureTokenServiceApplication is not configured properly in IIS. The ...


1

Yes, this should work if you attach all the needed cookies (should be FedAuth ... but there might be others). This is the same scenario as calling SharePoint online. It uses federated auth too. I blogged about how to authenticate with 365 here: ...


1

You will need to use Powershell to set the token life time of the security token service. the Default life time is 10 hours. You can find more information at How to Set Forms Authentication Timeout?


1

After a lot of debugging, I was able to figure out what was causing our issue. For some reason, our app pool was recycling frequently throughout the day. Users who were actively working on the site were losing their cookies if they had checked Remember Me. Some code we had in our custom chunked cookie handler was checking for the HttpContext.User ...


1

Robert Bogue has written a tool and sample app I have used successfully against a claims environment. Basically he extends the ClientContext class. In my case though, I had to be on a domain-joined machine for the code to work. Download it here.


1

In terms of Capacity the theoretical limit is 50 millions per Document Library, SP2010. Besides there is no practical limit to how many items per Container (e.g. Folder), but there are recommendations, up to 5000 (default configured as Threshold in CA for each Web Application). More on this, considering the amount of traffic estimated and groups, you would ...


1

Try reading Geoff Varosky's blog and MSDN on Claims-Based Single Sign-On for Microsoft SharePoint 2010 and the Guide, too. There may be some hints.


1

yeah i have seen this before as well, and it has hit me in production as well ;-) Are you using ProtectedData in .NET to encrypt passwords? http://msdn.microsoft.com/en-us/library/system.security.cryptography.protecteddata.unprotect.aspx my guess is that you are seeing this now because your production environment is multi-server, and your development ...


1

It is SP 2010? Did you tried: Central Administration > Security > General Security > Configure service accounts > [Select One] Service Application Pool - SecurityTokenServiceApplicationPool or shortcut to it: http://[CA url]/_admin/FarmCredentialManagement.aspx



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