Why is the security token service is not available?

Why is the security token service is not available?

Rule Name: The Security Token Service is not available. Summary: The Security Token Service is not issuing tokens. Cause: The service could be malfunctioning or in a bad state, or some assemblies are missing when you deploy the custom claims provider.

Why is my STS not issuing security tokens?

If this script throws errors, that means the STS on that server cannot issue security tokens. If you enabled IncludeExceptionDetailInFaults in the STS web.config like mentioned above, it should give you a decent error to research and fix, like the one detailed in the section below.

How to restart the security token service application pool?

Resolution: Restart the Security Token Service application pool. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. Identify the server on which this event occurs.

When do you do not need person tokens?

If you onboard only individuals, you do not need person tokens. Instead, create account tokens and pass the individual hash on the Account object to provide the required information. The first step is to create an HTML form that collects the required information for the account and the person.

Where to find windows exception for security token?

I have used the ULS view to track down the error to this: An exception occurred when trying to issue security token: The requested service, http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas could not be activated. See the server’s diagnostic trace logs for more information.

How to restart security token service in SharePoint?

The Security Token Service is not available (SharePoint Server) In the Application Pools list, right-click SecurityTokenServiceApplicationPool, and then click Start. If the application pool is started already, click Stop and then, in the Action pane, click Start to restart it.

Where is the security token service in IIS?

Moving one layer down, to the SecurityTokenServiceApplication: This one is running under the SecurityTokenServiceApplicationPool. Clicking on test settings here results in an error:

How to troubleshoot the security token service ( STS )?

When investigating STS problems, you should look at the ULS logs, Application Event log (event viewer), and even Central Administration. The built-in SharePoint Health Analyzer has a rule for testing STS functionality. It’s called “The Security Token Service is not available”. It runs hourly and will report if the STS fails on any of your servers.

Where do I find the security token service hotfix?

If the server is running Windows Server 2008 R2, the hotfix mentioned at http://support.microsoft.com/kb/976462 must be installed. Incorrect data in the configuration file: Please review the web.config file of the secure token service application and compare it to a web.config file from a “working” secure token service application.

Where is the custom claims provider in SharePoint?

A custom claims provider is installed in the farm, but is only deployed to the servers that are running the “Microsoft SharePoint Foundation Web Application” service. When other servers call their STS, it tries to load the custom claims provider, but fails because the custom DLL is not available on the box.

Can a SAML token issuer use SharePoint Server?

For a trusted SAML token issuer, SharePoint Server does not offer list or search. When a user enters some value, SharePoint Server always resolves it. This means that if you enter [email protected], the people picker accepts the value.