21-2
UserGuide for Cisco Digital Media Manager5.4.x
OL-15762-05
Chapter21 Proof of Play
Concepts
•
Implications of Changing the DMM Appliance Hostname, page 21-2
•
Implications of Changing the User Authentication Method, page 21-2
Implications of Changing the DMM Appliance Hostname
Will you use AAI to change the hostname of a DMM appliance on which proof-of-play features are
enabled (CSCtr00731)? There is no common reason to do this. We recommend that you do not.
Nonetheless, we will not stop you.
BEFORE YOU CHANGE THE HOSTNAME
•
Export your proof-of-play logs.
AFTER YOU CHANGE THE HOSTNAME
•
Log in to the web interface for DMM at its new hostname. Then, reconfigure the proof-of-play
feature immediately.
WHY IS THIS NECESSARY?
We assume that your information is confidential and we strive to protect it from unauthorized
access. Therefore, DMM self-registration of a feature license consider s the combination of the
appliance hostname and its hardware serial number.
After its appliance hostname is changed, DMM will reject its prior self-registration of your license to
use proof-of-play features. Although the license is still valid and is still correctly associated with your
hardware serial number, your DMM appliance cannot load proof-of-play logs from any server whose
hostname differs from its own. It cannot read from them or write to them. Likewise, you cannot use
proof-of-play features on any host but the one that self-registered the license.
Although you can return a hostname to its original value, doing so still might not be sufficient to satisfy
an ongoing requirement for full and uninterrupted access to proof-of-play featur es and logfiles. Consider
this scenario.
1.
The hostname is changed from A to B. Therefore, B cannot use the feature license that A
self-registered and cannot use the logfiles that DMM generated on behalf of A.
2.
The hostname is then returned to A. Therfore, A can access its own data from any time when the
hostname was A, including the original instance. However, it cannot use the feature license that B
self-registered and cannot use the logfiles that DMM generated on behalf of B.
We recommend that you prevent these complications and disruptions by leaving the hostname in its
original state.
Implications of Changing the User Authentication Method
Will you change the user authentication method from LDAP mode to Federation mode (SSO) for a
Cisco DMS deployment that includes proof of play (CSCtq55094)? Fundamental changes to user
authentication are not routine but can be useful occasionally.
However, account records in the new SSO user base might not correspond exactly to account records in
the old LDAP user base. It is possible, in fact, that some long-established login credentials might cease
to be valid for Cisco DMS users. And so, if the proof-of-play user role assignment in yo ur network is
associated with one of these nullified user accounts, the affected user cannot view proof-of-play
campaigns or run reports for campaigns.
In this case, you must assign the proof-of-play role to a user account that exists in the SSO user base.