This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 17%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
We have a .Net application which we implemented ADFS WSFED in it. Its working fine in local but when we deployed we are facing this error.
For Dev in URL I see Realm is HTTPS but wreply is HTTP.
But for local I see Realm is HTTPS but wreply is HTTPS. and Auth is working perfectly.
Tried so many methods, but still getting error: The same client browser session has made '6' requests in the last '1' seconds. Contact your administrator for details. ADFS WSFED.
Please give some suggestions.
Protocol Name:
wsfed
Relying Party:
URL
Exception details:
Microsoft.IdentityServer.Web.InvalidRequestException: MSIS7042: The same client browser session has made '6' requests in the last '0' seconds. Contact your administrator for details.
at Microsoft.IdentityServer.Web.Protocols.PassiveProtocolHandler.UpdateLoopDetectionCookie(WrappedHttpListenerContext context)
at Microsoft.IdentityServer.Web.Protocols.PassiveProtocolHandler.ProcessCommonCookiesInLastAuthenticationStage(ProtocolContext context)
at Microsoft.IdentityServer.Web.Protocols.WSFederation.WSFederationProtocolHandler.SendSignInResponse(WSFederationContext context, MSISSignInResponse response)
at Microsoft.IdentityServer.Web.Protocols.WSFederation.WSFederationProtocolHandler.Process(ProtocolContext context)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.ProcessProtocolRequest(ProtocolContext protocolContext, PassiveProtocolHandler protocolHandler)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)
Hi @rody , this can happen when the same client browser session makes multiple requests in a very short period of time.
Check that the Realm and wreply URLs are consistent across your environments. In your case, it seems like the wreply URL is HTTP in the development environment and HTTPS in the local environment. Make sure both URLs use HTTPS to avoid any inconsistencies.
The error shows that the loop detection cookie is being triggered. This can happen if the client is making multiple requests in a short period. You can try increasing the loop detection threshold in the ADFS configuration. This can be done by modifying the LoopDetectionThreshold parameter in the ADFS configuration file.
Make sure that your ADFS server is up to date with the latest patches and updates.
Please let me know if this works!
Best,
James
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
this error is from redirect errors. the login server has detected a login loop. that is after login, it redirects to the application site with the token and the application site redirects back to the login site.
try an oauth debugging tool for the browser to see what is happening.