Bug 13178 - Review behavior when changing music servers
: Review behavior when changing music servers
Status: NEW
Product: SB Radio
Classification: Unclassified
Component: Connectivity (Server)
: Include FW version in comment
: PC Other
: -- enhancement (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-31 16:13 UTC by Dan Evans
Modified: 2011-11-06 23:23 UTC (History)
4 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-07-31 16:13:52 UTC
Testing 6865.

Currently if you are connected to SB Server, but the server does _not_ have your SN credentials entered, you get an error when selecting either "My Apps" or "App Gallery" :

"Problem Connecting ... A mysqueezebox.com account is required for this service. Please access Squeezebox Server Settings > mysqueezebox.com with a web browser to configure."

This error should be unnecessary.  My Baby is registered on SN and should be able to access most services.

(I suspect this is a dupe of an existing issue, but I couldn't find a bug on this.)
Comment 1 Wadzinski Tom 2009-08-03 04:56:12 UTC
What should happen in this case? Should an SC that doesn't have SN credentials 
use the player's credentials?
Comment 2 Andy Grundman 2009-08-03 10:06:13 UTC
Hmm good question... 2 options: SC stores credentials from a connecting SP player, or SC just passes it through for each specific request made by that SP.

Option 2 probably makes more sense to the user.
Comment 3 Weldon Matt 2009-08-03 10:22:40 UTC
Seems like yes, SC should use the credentials entered into the player.

If there are NO credentials that can be found on either the player or SC (an edge case, but it will happen if we allow the back-door non-internet setup), we should present some sort of screen saying "This feature requires an account from mysqueezebox.com," with options to create an account or log in.
Comment 4 Andy Grundman 2009-08-03 10:39:44 UTC
So would SC take on the credentials of the first SP that used it, or would the credentials be passed-through on a per-request basis?  This probably has more implications for MV than normal users.
Comment 5 Ben Klaas 2009-08-26 07:53:29 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 6 Wadzinski Tom 2009-10-03 12:41:15 UTC
Andy, any idea where we stand/ is anything planned on this?
Comment 7 Andy Grundman 2009-10-04 05:04:50 UTC
A player does not actually store any credentials so this is not a trivial thing to implement.
Comment 8 Andy Grundman 2009-10-08 11:22:49 UTC
Tempted to mark this won't fix.  Dan how serious is this?
Comment 9 Dan Evans 2009-10-20 08:24:04 UTC
I'd say this is important.  

Of the questions coming in post-7.4 launch, confusion over server connections or what server do I connect to or how do I connect to mySB.com when I turn off my computer are high.

This bug may not be named correctly. (it's too broad?)  To this specific issue...  

Improving the intelligence of SC to connect to an existing account could create one of those "OOoooh" moments for our customers where "it just works".  Rather than making a customer jump through the same hoop twice, or worse just being confused why it doesn't work.  (Bear in mind, from the customer's perspective they have *already* created the needed account and this error may make no sense.)
Comment 10 Chris Owens 2009-10-21 09:47:41 UTC
Moving these bugs to P4 to make room for moving P1.5 bugs to P2
Comment 11 Pat Ransil 2009-10-23 05:09:42 UTC
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Comment 12 Chris Owens 2010-03-08 11:26:49 UTC
Moving lower-priority bugs to next target
Comment 13 Alan Young 2011-11-06 23:23:42 UTC
Unassigned bugs cannot have a priority.