Change address of the CMS remotely

Change address of the CMS remotely.

When there is a need to change the display to a CMS that is hosted on another address is required to go personally to the display to change the server address and password.

How about offering the possibility to change these two data remotely via CMS? so after changing the player would be restarted automatically and would connect the new CMS.

Imagine how much time would be saved. :slight_smile:

I certainly appreciate you would save some time doing this - this would be trivial to implement. However, we’ve not implemented it for the security considerations - (you wouldn’t want someone else taking ownership of your display)

But this change will be made in the CMS Administrator area, only the administrator has the password.

The only way to do this is someone with the password.

Still, to increase security, and if it were added a password display, which would be necssária to make this change? would work?

I second the want for the feature.

I think if you tied it to say an administrator email, that would need to link clicked with a key to verify the user, it might work.

1 Like

Perhaps we could make this functionality available through XMR only - and via a multitude of “are you sure” dialogs.

3 Likes

Works for me. 20Chars

1 Like

Looking forward to this feature

1 Like

The other thing to consider is what if the user enters a CMS address that doesn’t exist? Or that uses a different key?

You then have Players that can’t register, and are no-longer connected to a CMS to control them.

Good point. So then the player would need to make sure that it can communicate to the CMS at the new address before accepting the changes. If that fails I guess it would then revert to the previous address used?

Starts getting very complicated - especially if that CMS is then telling it to move to the address it can’t register to!

I see the need, but the solution needs very careful consideration.

So we would have:

  • A form on the display page to “move to another CMS”, which opened and asked for a CMS address
  • Selecting OK sends an XMR message to the player containing the new address
  • The player pings the new address asking for the XMDS version (to confirm that Xibo exists at that address)
  • If it finds it, it re configures itself against the new address and registers
  • If it doesn’t, then it does nothing

And then what happens to the display record in the old CMS - it is left there for the user to decide whether to delete it or to un-authorise it? How does the user know it worked? Perhaps the player would also need to notify its status back to the CMS?

As Alex says, it starts getting rather complicated :smile:

I would think the display entry in the previous CMS would be removed, as the display is no longer linked to the system. BUT…What about the statistics/Proof-of-Play? I would see no logical way of migrating those either since the stats rely on IDs. They would be lost for good if the display is removed from the previous CMS.

So then how to deal with that? Maybe it doesn’t get deleted but lives on temporarily in some strange state till all the statistics for the display expire in the previous system? Or some way the log is converted, but then how do you deal with that?

Seemed such an easy request when it was first brought up.

As you say, I don’t think proof of play can or should be migrated.

At present if you deleted the display after a successful migration (I am still not sure how you’d know that it was successful from the original CMS), then the stats would effectively disappear. They would still be there in the table, but wouldn’t link to anything.

I think this question really comes down to how we aggregate stats in the future - storing every single instance of a statistic is probably not the optimal solution going forwards and some sort of aggregation will need to be developed. That is for another topic though!