Hot answers tagged

4

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


3

It sound's like the web applications get a timeout and does not get created correctly. I've had this problem in both production and staging environment, and changing the time-out has worked perfect both times. This is usually because you either have too many Web Applications in your SharePoint Server, or because your SharePoint Server is slow! As part ...


3

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


3

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


3

I think Sharepoint doesn't support SAML v2.0 even we are talking about WIF. I tried to handle SAML 2.0 token in Sharepoint but unfortunatelly it seems that doesn't work so far, like sharepoint engine can't do that ;/


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

Yes, you would setup an ADFSv2 server, then use SharePoint in Claims mode. When a client logs in, they will access the ADFS server, then redirect into SharePoint. This is the same way Office 365 uses for authentication.


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

It is highly recommended Security token Services should run the services account( i would prefer under farm admin) not under the local system account. You know STS is very important services application and run on every server in the farm. This account is used as the identity for the service application endpoint application pool. This account must be the ...


2

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


2

Answering your first question - The "Expiration of the session" depends on SAML TokenLifetime and LogonTokenCacheExpirationWindow values. It doesn't depend on the cookie value. The cookie value is just a reference to the actual SAML Token. It is not an indicator of session validity. Regarding your second question, you may not want to increase the ADFS ...


2

Disable loopback check or specify allowed host names. The two methods are described here.


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

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

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

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


1

you can get the access token by making a POST request to https://accounts.accesscontrol.windows.net/<site_realm>/tokens/OAuth/2 with required post parameters in the body. this will return the access token and refresh token which you can use to make REST calls to sharepoint online site and to regenerate the access token once it expires. refer this ...


1

There could be multiple reasons why the Security Token Service doesn't start. For example, the service account doesn't have the correct permissions (Logon as a Batch Job for Application Pool). In the ULS Logs you will probably find more, and also check the System Log of Windows.


1

You can try following workaround. It might help you. Open Internet Explorer 10 Press ALT Click Tools > Compatibility View Settings In the “Add this website” box add the following sites using the Add button sharepoint.com dynamics.com Click Close Now when you refresh the page you should see the Browser Mode correctly represented as Browser Mode “IE10 Compat ...


1

I had the same issue on a server with two IP addresses. I modified the hosts file to point "localhost" to the first IP address (which the STS was bound to), and that solved the problem. I am not a windows systems expert, so I don't know if that is a bad idea for other reasons.


1

On the SharePoint side, no. In a Provider-hosted app, it is the responsibility of the remote web to authenticate the user and pass that identity to SharePoint as part of the token. If you have trusted the app to make app-only calls, then you have to trust the app. :)


1

The last commands did solve this in my case, I also had to run an IISRESET on all serverns in the farm More information http://support.microsoft.com/kb/2545744


1

I also ran into this problem, but in my case it was very simple to resolve: The SharePoint Web Services site was stopped; once it was started the problem disappeared.


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


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

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

to be honest I've discovered this is out of the realm of SharePoint, we just needed something generating SAML tokens with 2 attributes in the assertions, it was easier to code something up using this componentspace.com/Products/SAMLv20.aspx. Thanks everyone for your help.


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

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



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