The initial setup process is easy. It's straightforward, but as far as integration, the complexity will depend on the application and how those applications will be integrated. 

For implementation, generally, you will require one to two people, including an architect and implementers. 

The support of the user interaction was the only issue. The only issue we had with the initial setup was configuring the certificate-based SAML integration between our SSL VPN service and the CA Advanced Authentication service. There was a minor issue that we were able to resolve in about 30 minutes of troubleshooting.

Other than that, the initial setup went very smooth. Getting users to self-enroll in the service was the next challenge but it was overcome with good communications to the field and the service desk where users would call in trouble tickets.

Straightforward.

I was involved in the setup as the solution architect. I did everything on the project to release it to the production environment. It was a complex process because we are talking about a security project. When we talk about this kind of product, it is normal for it to be complex.

I was not involved in the setup.

Sometimes getting this set up does take a bit longer. It's not always install, next, next, next, finish. We have so many requirements that we're trying to meet again either from Contractual or Federal standpoint that we're not always the easiest to configure for. We have a lot of special cases and we'll present a lot of challenges to them that again they'll help us like, "Well, to do this, you're going to need this, this, this and this." And again, help us get all the right pieces in place wherever they need to be, working the way they need to and deployed.

Initial setup was medium-to-high complexity because everyone -- process, business, technical, application people -- needed to be involved. We needed to set many standards and be advised by many committees to make the setup a success.