If you have an error similar to this:
“System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo)”
This issue might be caused by the SecurityTokenServiceApplication being stopped in the IIS.
You can check by going to the IISManager-> Sites -> Sharepoint Web Services -> SecurityTokenServiceApplication.
You can start by checking if the Sharepoint Web Services are started.
After that you can check in the SecurityTokenServiceApplication providers if they include your membership providers configurations.
For me it was that the problem, once we started the Sharepoint Web Services and configured the membership providers all started to work again.