I would suggest putting all the single sign-on functionality needs into a business requirement document that is specific to your company and making sure there are a robust set of tests throughout the project to ensure the servers retain all of their single sign-on capabilities. A good way to determine appropriate test criteria is to find your documentation set from the original SSO implementation by pulling your business requirements document, your technical requirements document and your SSO testing data. Review it to make sure that it still makes sense for the business and use the language and test steps from them to make sure virtualizing the servers won't have any negative effects on the business.
For more information:
Dig Deeper on Single-sign on (SSO) and federated identity
Related Q&A from David Griffeth
Are users at your enterprise creating weak passwords that could potentially lead to serious data breaches? In this identity and access management ... Continue Reading
Periodic access reviews for enterprise identity and access management (IAM) can help ensure the necessary personnel have access to essential systems ... Continue Reading
When an enterprise gets new IAM systems, training employees on how to interact with the technology is one of the most important aspects of deployment... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.