How can we improve Summon?

Add the option to force Summon to load over https

In October, Google Chrome release 62 will begin labeling any website loaded over http and containing a form (i.e. every library webpage ever) as "Not Secure." You can read more about that here: https://security.googleblog.com/2017/04/next-steps-toward-more-connection.html

We currently have all our links to and search forms use HTTPS to access Summon, but we can't force all our users onto HTTPS. Since the *.summon.serialssolutions.com wildcard certificate covers every instance of Summon, why not add an option to force all Summon connections to use HTTPS? (Or just make it the default.)

While you're at it, why not add your exlibrisgroup wildcard certificate to your User Voice account so that I can enter a password for this Ideas group on a secure page, rather than an insecure one? ;)

96 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Matthew Reidsma shared this idea  ·   ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Virginia Dearborn commented  · 

        Yes, please! Forcing HTTPS would be very much appreciated here.

      • Suzy Bailey commented  · 

        Great idea. I just want to highlight an issue for us - ProQuest/ExLibris manages our custom script and hosts it at http://local.4libs.org/ - they don't support https to my knowledge, so ideally alternative hosting arrangements would be considered as part of this improvement.

      • Debby Andreadis commented  · 

        This is a great and necessary idea. Thanks for posting it Matthew.

      Feedback and Knowledge Base