Blog Viewer

Six Considerations for Accelerating a CA SSO Implementation

By Pashapour posted Sep 11, 2017 06:40 PM


In our final post on migrating to a CA SSO solution, we will present six things you need to keep in mind if you want to accelerate the project. There is no standard timeframe for implementation of CA SSO; the speed of implementation is dependent upon a wide range of factors. These factors especially impact implementation timelines:


  • Existing authentication(s): The number and type of authentication and session management mechanisms currently in place to protect web applications affects implementation complexity.
  • User stores: The number and type of existing user stores and migration and synchronization requirements affect project progress. 
  • Custom code requirements: Requirements related to custom authentication schemes, active responses and policies or advanced functionality not supported by the current product can have a negative impact on production timelines.
  • Availability of hardware: Long hardware lead times often have a negative impact on rapidly moving the implementation beyond the development phase.
  • Resource availability: If an organization cannot dedicate the enough resources to provide the necessary info for requirements gathering and help generate designs, the process will be prolonged.
  • Modifications to legacy applications: A company must have developers familiar with the applications being integrated into the architecture and be able to modify applications as necessary. Modifications to legacy applications are sometimes a large undertaking; if the applications aren’t ready when the solution infrastructure is available, the timeline will be affected negatively.


If you are interested in exploring CA SSO implementation options contact