We already use a well-established and supported SSO product in the company. As I was looking at doing SSO with CUCM 8.6, I was mystified on why the application dictates what SSO product (OpenAM 9.0) it works with. This contradicts any architectural reasoning. The application should be agnostic to the access mgmt product.
The SSO product we use can do all the things that OpenAM does and much more, and there is nothing in the SSO CUCM 8.6 config white paper that seems to indicate a intrinsic tie-in to OpenAM.
Can someone please tell me what in the application is driving this requirement? Do you know of examples where companies have done SSO in CUCM without OpenAM.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...