I've worked with multiple clients in the past to configure OTM SSO with Netegrity, though they had admins who handled the configuration of the product itself. From past experience, can you ensure the following have been done:
- Ensure OTM has been configured to work with a reverse-proxy and the URL-prefix is configured
- Ensure that Netegrity is configured to key off of this URL-prefix and remove it before passing the URL back to OTM
- Ensure that Netegrity is configured to retain session cookies from OTM in order to maintain session integrity
--Chris