Can’t Debug with SSO after MS 10-70 (and other) updates RSS

• • Reply
  

  doas777

  Member

  8 Points

  6 Posts

  Can’t Debug with SSO after MS 10-70 (and other) updates

  Aug 12, 2011 06:24 PM|LINK

  Our organization uses an SSO system based on the Membership and role providers largely based on this specification. The SSO has been deployed for years and works like a charm for the most part.

  Over the last 9 months, we have found that when one of the MS 10-70 patches is applied to a development box, the developer can no longer debug their projects, because whenever they attempt to login, the system simply redirects back to the sign-in page.</p> <p>We have blocked the MS 10-70 updates on our wsus server, and that has worked for us, until just recently. Now however, newly installed machines with nothing but VS2008 SP1 and updates are no longer able to debug SSO-enabled projects.

  Does anyone have any ideas on how to get our developers debugging again? I have to assume others have had this issue as well. Thanks!

  Tubalcane

  • Edited by doas777 on Aug 12, 2011 06:28 PM
  • Edited by doas777 on Aug 12, 2011 06:30 PM
  • Edited by doas777 on Aug 12, 2011 06:30 PM
  • Edited by doas777 on Aug 12, 2011 08:31 PM
• • Reply
  

  doas777

  Member

  8 Points

  6 Posts

  Re: Can’t Debug with SSO after MS 10-70 (and other) updates

  Aug 16, 2011 05:03 PM|LINK

  Well, a little progress. It appears that Windows7 SP1 includes two updates from MS 10-70 (KB2416471 and KB2416754), so after applying SOP1, our .net 3.5/VS2008 developers cannot debug. But refusing to install a service pack is not really an option, so still trying to figure out why these updates kill our debugging with sso.