Access to our support articles is only relevant to users who are logged into our service. Particularly, when a user is having a problem, it seems like the worst time for them to sign up or login to yet another system they don't understand.

Combined with the fact that I cannot delete bogus submissions (http://feedback.uservoice.com/forums/1/suggestions/6429242), this makes the omnibox a security bottleneck.

I was going to send an email campaign to our users collecting feedback, when I found that SSO is not supported by the satisfaction widget (and none of the omnibox widgets for that matter). Was there any particular business rationale behind this decision?

The omnibox widget seems to only accept email/name pairs in plain text, which makes it very vulnerable to tampering.

We have private sites with only private forums for our general product lines, internal suggestions forums, as well as our many Beta Tests. When a customer or staff member is within one of our web applications, we want them to be able to provide feedback from within the page (authenticating using SSO), and not have to log into a UV site. We've been trying to reduce the log in authentications our customers have to go through and this is hindering that progress.

Plus, the classic widget had this, which is feature we need but lacks the new design and features that resembles our own design standards.

We also are setting up private forums with SSO and the new widget, out of the box, fits much better with our design and is much easier to work with overall (I love it over the classic widget). Without it supporting SSO we will have to stick with the classic widget which is not nearly as nice.

We would really like to use the new widget but we cannot switch over to it until the SSO support is available. We currently have the classic version integrated via SSO so that our users who are logged into our products do not have to go to the bother of creating users within UserVoice (and also helps ensure that ideas are coming from our customers actually using the product rather than unknown people).

We are just getting setup. We are also implementing SSO and are using a private forum. A subset of our users will be granted access to this private forum via SSO. We'd like the widget to know the user has access to this private forum so it can present those ideas and encourage posting. I assume you're planning this as you did with the classic widget, please let me know. In the meantime we are dumping the new widget entirely and implementing the classic one.

@Joshua - Yes. Our Word press forum site is completely private for use by our customer base so I implemented SSO on the classic widget to allow users to post an idea into Uservoice. However I really like the look and functionality of the new widget. Especially presenting the ability to vote between 2 ideas. This will help get new users into the spirit of voting. But unfortunately since the new widget does not support SSO I need to stick with the classic Widget for now.