Connecting Screens in Concerto 2

[Michael Carpenter]

Greetings,

I'm testing Concerto 2 right now and deploying it on a dev server after doing the same with Concerto 1. With Concerto 1, I could simply pass a URL with a registered MAC address encoded in. I've been having a world of woe finding something equivalent in Concerto 2. The blog says Concerto 1 URLs are backwards compatible with Concerto 2, but how do I register a new screen? There is no MAC address form when I add new screens and the screens table in mysql only has an "authentication_token" that is completely blank. I'm probably missing something obvious, but the wiki isn't very helpful and I'm basically searching through ruby code, hoping that I might be able to spot the mechanism itself. In Concerto 2, how does one deploy a screen from scratch as of Foxtrotflamingo?

Thanks!
- Michael

[Michael DiTore]

Hi Michael,

The best way to set up a generic screen right now is to point the homescreen of the browser at the "frontend" URL for the screen, which depends on the screens database ID. For example, if the screen's information page in the Concerto Panel is http://your-concerto-server.com/screens/3, then you can simply point your screen to http://your-concerto-server.com/frontend/3.

Right now the MAC address backwards-compatibility is only really accessible upgrading an existing Concerto install (though that may change). We want to move away from the MAC address as the primary identifier because it doesn't really add any security and can't really be found automatically through the browser (unless using the concerto player OS). However, if you have a client that requires using the MAC address going forward, we can provide instructions on getting at that feature through the console.

Improving the screen registration process is an ongoing project right now. The envisioned workflow is that all screens will simply point at the same URL, /frontend, and display a secure configuration code that you can then enter into the panel, so no interactivity/setup is needed on the screen, as long as the screen can store a persistent cookie. (The in-progress github pull request is here.)

Let us know how this works for you.

Mike

- Michael

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-s...@googlegroups.com.
To post to this group, send email to concerto-dig...@googlegroups.com.
Visit this group at http://groups.google.com/group/concerto-digital-signage.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Michael Carpenter]

Thank you so much for this clarification. This is significantly simpler than I thought. One final question if I may: where does authentication with CAS and LDAP stand? Is it possible yet? The wiki has drafts and plans for it, so I'd assume it's not implemented yet.

Thanks,
- Michael

[Brian Michalski]

You're correct.  It's not yet possible in Concerto 2, but certainly on our radar.

Thanks,

~Brian M

--

[Joffrey Le Fevre]

Did anyone get a request for pasword and username while surfing to the url? If so wich pw do they need?

Op dinsdag 23 juli 2013 22:11:07 UTC+2 schreef Brian Michalski:

You're correct.  It's not yet possible in Concerto 2, but certainly on our radar.

Thanks,

~Brian M

On Tue Jul 23 2013 at 1:55:14 PM, Michael Carpenter <konu...@gmail.com> wrote:

Thank you so much for this clarification. This is significantly simpler than I thought. One final question if I may: where does authentication with CAS and LDAP stand? Is it possible yet? The wiki has drafts and plans for it, so I'd assume it's not implemented yet.

Thanks,
- Michael

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.

To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-signage+unsub...@googlegroups.com.