Zum Hauptinhalt gehen

Displaying secure WMS in HTML5 2.4.1 viewer

Kommentare

7 Kommentare

  • Permanently deleted user
    Just did a test with the Authentication Settings under the 'Edit Connection Settings' button, and it does not seem to matter what you type in here, it always passes the test! (proxy is blank)

     

    Bizarre...
    0
  • Permanently deleted user
    Hi Gareth. Did you get anywhere with this? I'm having similar problems...
    0
  • Permanently deleted user
    No David

     

    - absolutely nowhere! We've ditched the HTML5 viewer for the moment while they come up to speed with things like advanced editing, so it's been on the backburner I guess you could say. I'll be testing again in the next few weeks with hopefully 2.7 and see how that goes?

     

    fingers crossed :)
    0
  • Permanently deleted user
    We've also shelved a lot of our HTML5 viewer development work until next year when hopefully a lot of the current issues will have been fixed and the existing features will have been enhanced.

     

    We can actually access secured WMS' in HTML5 viewers by going via a proxy that stores the WMS' credentials (the proxy was provided to us by AAM several years ago). The trouble is, within Chrome, users are still prompted for a username/password to access these services. However, regardless of how the users respond to the prompt (correct credentials, incorrect credentials, canceling out of the dialog box) the connection is still made successfully! The prompt servers no purpose other than annoying the end user. In IE, there is no prompt and it just works.
    0
  • Permanently deleted user
    Interesting behaviour across the browsers..

     

    I might chase this up again with AAM, and add it to the list of items we are seeking more clarification on.
    0
  • Permanently deleted user
    Any update on this? I'm currently having the same problem with GVH 2.10
    0
  • Patrick Fingler
    I believe this is related to GVH-3814 (Secured WMS service does not prompt for credentials in Chrome).  This was originally filed as a bug but has been resolved via a 3rd party fix through Google Chrome. 

     

    The issues that you are encountering are likely due to Chrome's default security settings. 

     

    https://stackoverflow.com/questions/8913730/chrome-fails-to-show-http-authentication-window

     

    Google Chrome doesn't allow for cross-site authentication for resources as protection against phishing attacks. Should you want to use Google Chrome with secured WMS services you must run chrome.exe with the --allow-cross-origin-auth-prompt flag. 

     

    Please let me know if that helps!

     

     
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.