Author
|
Topic: WM STB w/out Pin (Read 959 times)
|
vpngolfer
Jr. Member

Karma: +0/-0
Posts: 4
|
In following the documentation I understood that I could run a stb without having the user enter a pin. (The Microsoft AD LDAP and VBrick LDAP are turned on since we are using SSO with ActiveDirectory.)
It can authenticate by hostname or IP was my understanding. Could someone provide some details on how this is accomplished.
Right now I have an stb configured in the user area of mcs admin and the pin works fine. I have the hostname of the stb on the stb itself and MCS portal the same. Also, if I was curious if anyone was running ssl on the login page of MCS portal? I have done this and it works great, but then a pop up comes up on the stb asking if the site should be trusted, then the 'page cannot be displayed message appears. Which makes since, because there is trusted root ca's on the stb's like in IE.
|
|
|
|
|
rmavro
Administrator
Hero Member
   
Karma: +5/-1
Posts: 294
|
In following the documentation I understood that I could run a stb without having the user enter a pin. (The Microsoft AD LDAP and VBrick LDAP are turned on since we are using SSO with ActiveDirectory.)
It can authenticate by hostname or IP was my understanding. Could someone provide some details on how this is accomplished.
Right now I have an stb configured in the user area of mcs admin and the pin works fine. I have the hostname of the stb on the stb itself and MCS portal the same. Also, if I was curious if anyone was running ssl on the login page of MCS portal? I have done this and it works great, but then a pop up comes up on the stb asking if the site should be trusted, then the 'page cannot be displayed message appears. Which makes since, because there is trusted root ca's on the stb's like in IE.
You simply need to specify the STB in the MCS configuration. How to do this is explained in the MCS manual. Please post the page number of the manual that confuses you and perhaps we can further explain?
|
|
|
|
|
vpngolfer
Jr. Member

Karma: +0/-0
Posts: 4
|
Thanks for the reply, here is where I'm at...
I'm referencing pages 44-45 of Portal Server Admin Guide v4.2.
I configured a new STB as with following information: Hostname (not in DNS) IP Address (10.x.x.x) STB Model (ETV-IPR revision C) Start Mode (MCS)
I then hit the Submit button. When I go back to the list of STB’s, select the one I just created, and click Modify and Submit, the follow is displayed: STB Configuration Host Name Break Room IP Address 10.x.x.x User Name root User Password *********** Confirm Password Software Revision STB Model ETV-IPR revision C Start Mode MCS
Questions: 1) Where does the STB username and password get used in the STB authentication process? How are credentials validated? Must a user be defined in MCS to match the user associated with the STB? 2) What is the default system defined password value if left blank when adding a STB? 3) Must the hostname be in DNS? Must we use the FQDN? 4) From the admin guide, “The only time you will manually complete the STB Configuration fields is when you are defining the configuration for an STB that will be added to the network at a later time.” We do not get (and cannot choose from) a list of STBs that are broadcasting SAPs as specified at the top of page 45 (Select STB); only “STB Configuration” is viewable. What configuration is required to get a populated list? 5) When SSL is enabled, can STBs be excluded from using https?
|
|
|
|
|
amyg
Full Member
 
Karma: +3/-0
Posts: 9
|
For WM IPRs - you need version 4.2.1.6 to support that feature of not having to enter a PIN. Please contact your inside sales representative for an upgrade path.
|
|
|
|
|
ctsang
Jr. Member

Karma: +0/-0
Posts: 3
|
For WM IPRs - you need version 4.2.1.6 to support that feature of not having to enter a PIN. Please contact your inside sales representative for an upgrade path.
We just upgraded our portal server to 4.2.1.6. The WM IPR still asks for the PIN even though we set it up in the "Users" section as an "IP Receiver". So they don't have a PIN but it is asking for one when it powers up. Any idea?
|
|
|
|
|
amyg
Full Member
 
Karma: +3/-0
Posts: 9
|
Ahh...so the second piece of information that I learned with this. Not only do you need 4.2.1 you also need to make a configuration change on the WM IPR if you don't have a multicast enabled network. You need to change the SAP IP address on the WM IPR to the IP address of the Portal - the port number can be left unchanged. But instead of 224.2.127.254 for the SAP address you need to configure the IP address of the Portal in that field.
Once I did that I was rolling...oh and I need to change the Portal server address in the start up mode to the fully qualified name with domain name...but that's another story.
Good luck....
|
|
|
|
|
|
 |