Locked Server Error in '/' Application.

  • Monday, August 13, 2012 12:56 PM
     
      Has Code

    Hi All,

    Recently started using VSTS Ultimate 2010 for performance Testing. I have recorded a simple Login page where the login will be redirect to 3rd party.

    I am getting the below error page. It would be grateful if some could helpout with an example or a solution.

    ID4223: The SamlSecurityToken is rejected because the
    SamlAssertion.NotOnOrAfter condition is not satisfied.
    NotOnOrAfter:
    '8/13/2012 7:32:07 AM'
    Current time: '8/13/2012 12:37:39 PM'

    Description:
    An unhandled exception occurred during the execution of the current web
    request. Please review the stack trace for more information about the error and
    where it originated in the code.

    Exception Details:
    Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: ID4223: The
    SamlSecurityToken is rejected because the SamlAssertion.NotOnOrAfter condition
    is not satisfied.
    NotOnOrAfter: '8/13/2012 7:32:07 AM'
    Current time:
    '8/13/2012 12:37:39 PM'

    Source Error:
    An unhandled exception was generated during the execution of the
    current web request. Information regarding the origin and location of the
    exception can be identified using the exception stack trace below.

    Stack Trace:
    [SecurityTokenExpiredException: ID4223: The SamlSecurityToken is rejected because the SamlAssertion.NotOnOrAfter condition is not satisfied.
    NotOnOrAfter: '8/13/2012 7:32:07 AM'
    Current time: '8/13/2012 12:37:39 PM']
       Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateConditions(SamlConditions conditions, Boolean enforceAudienceRestriction) +906
       Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token) +461
       Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token) +117
       Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri) +151
       Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request) +583
       Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) +500
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270
    

All Replies

  • Monday, August 13, 2012 4:03 PM
     
     

    Sounds like your recording isn't capturing the SamlSecurityToken properly. From the error message I suspect a static token has been recorded and when you're trying to re-use it in the test you're (quite rightly) being told it's invalid.

    Does a manual run through the same pages work for you? If so you'll need to find out where and how the token is given to the user and most likely add an extraction rule to your test so this field can be captured and used on the fly for each test.


    Nick Sandel (Software Tester) New to C# since November 2011

  • Tuesday, August 14, 2012 3:13 AM
    Moderator
     
     Answered

    Thanks for Nick’s positive participation.

    Hi AVI2VSTS,

    Thank you for posting in the MSDN forum.

    The web test recorder does not record everything in HTTP communications. And there may be times when either the web test recorder or web test playback viewer does not accurately reflect what is actually getting sent over the wire in subtle ways. Sometimes we can use Fiddler to record real time communications between a browser and a server to find out the deviation.

    The link below about the similar question may help you:

    http://social.msdn.microsoft.com/Forums/en-US/Geneva/thread/0729aa6c-a5b7-4702-a9a5-e142fc390a26/

    If you want to avoid NotOnOrAfter parameter in the SAML token, the link below may be helpful:

    http://social.msdn.microsoft.com/Forums/en-US/Geneva/thread/ff0fc294-aae6-489e-9bc9-3d68476ec3a8

    If possible, you could provide more detailed information about the SamlSecurityToken or your SamlAssertion.NotOnOrAfter condition for helping to resolve the issue.

    Thanks,

    Amanda


    Amanda Zhu [MSFT]
    MSDN Community Support | Feedback to us

  • Wednesday, August 22, 2012 6:08 AM
    Moderator
     
     

    Hi AVI2VSTS,

    What about your issue now? Have you resolved it?

    Would you mind letting us know the result of the suggestion?

    Thanks,


    Amanda Zhu [MSFT]
    MSDN Community Support | Feedback to us