SSO Incident – ROOT CAUSE ANALYSIS – 6/4/2012 4:13PM PDT

On 5/21/2012, while performing some upgrades on our Single Sign-On (SSO) server, a service was switched on that inadvertently changed a configuration file that aided in customer logins. We were unaware that this fairly standard process would automatically change configuration files.

Action taken: Once this was realized, we reverted back to the configuration file that preceded it.

Steps to Mitigate: We have configured our SSO server to ensure that files would not be auto-written in future upgrades.

This entry was posted in Uncategorized and tagged . Bookmark the permalink.