Hoppa till huvudinnehållet

HTML5 viewer loads up twice

Kommentarer

10 kommentarer

  • Permanently deleted user
    Hi Ravin,

     

    I believe that is expected behaviour you are seeing, it sounds like the viewer is "single signing" you on.  It is a.k.a. SSO and there is an article here about it - https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA360000000CiWTCA0

     

    I believe you are seeing the initial viewer load with you not signed in, and then a subsequent load with you signed in.

     

    Regards,

     

    Wayne Richard

     

    Latitude Geographics Group Ltd.

     

    Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

     

    Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

     

    Developers of Geocortex web-based mapping software | www.geocortex.com

     

    An Esri Platinum Business Partner

     

     
    0
  • Permanently deleted user
    We have also seen this behaviour since denying anonymous access/only allowing authenticated users to our new HTML5 site.

     

    Wayne, you say this is expected behaviour, but why? Why should the site have to load once, only to load again to authenticate the user?

     

    Is there no way to pass through authentication with the first load of the site?

     

    I believe that this double-loading is a large part of the slow launch times we (and presumably others) are seeing, and any solution to this issue would be much appreciated!
    0
  • Nico Burgerhart
    What if you added the following to the viewer URL? &idp=AD AUTHORITY

     

     
    0
  • Permanently deleted user
    That is close to what they had me add to my URLs to have them go directly to AD - for me, the LG tech had me do something which I forget, to create the following:

     

    https://maps.srcity.org/Geocortex/Essentials/REST/security/signIn?token_type=fragment&app=https%3a%2f%2fmaps.srcity.org%2fHtml5Viewer%2fIndex.html%3fviewer%3dSantaRosaMap&idp_name=AD+AUTHORITY

     

    from the original

     

    https://maps.srcity.org/Html5Viewer/Index.html?viewer=SantaRosaMap
    0
  • Permanently deleted user
    Thanks very much for the suggestions Nico and Mike!

     

    I have tried Nico's suggestion, but I don't think that URL parameter is valid for us, using the following shortened URL format:

     

    https://[organisation]/[virtual directory]/index.html

     

    As we are only using one viewer, we have set it as our "default" in the index.html file. This allows us to simplify the URL and keep it the same after upgrades (i.e. the URL does not include the Geocortex version number).

     

    However, it seems that this approach isn't compatible with the URL parameter posted, as it returns a Runtime Error.

     

    On the other hand, it does work, if I use the longer URL of the format:

     

    https://{organisation]/[GXEInstance]/index.html?viewer=[ViewerName]&idp=AD AUTHORITY

     

    But using a different base URL is not really a solution for us...

     

    It seems that the approach posted by Mike is in keeping with the HTML5 Administrator and Developer Guide (pp. 50-52), but again, not feasible in our circumstance.

     

    Do you know of a way to include this configuration somehow in the index.html, or other associated files?

     

    Wayne, is this an opportunity for future enhancement, or does this option already exist?

     

    Thanks again all, and apologies to Ravin for hijacking your post. :)
    0
  • Permanently deleted user
    I find this post interesting as we are looking for each opportunity to minimize the startup time. Thank you all for the input.

     

     
    0
  • Permanently deleted user
    @ Jamal - It's important to note that adding the functionality suggested by Lindsay would increase loading time. This is because it's extra code which has to load and do a synchronous call to confirm identity before loading anything else.

     

    Indeed, the only way to decrease loading time is to hit the authenticating entity first with parameters in the URL like Mike suggested. 
    0
  • Permanently deleted user
    Thanks Matthew,

     

     

     

    That’s correct. However, I have reported longtime ago that during the GVH\GVS launching process, the geocortex calls many links which is time consuming. Other extra links are also called in case of setting permission plans.

     

     

     

    Also, I have recently reported that the GVH can land with two forms of links as filed here with no idea how the geocortex choose the final landing link:

     

    https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&id=90660000000CkjFAAS

     

     
    0
  • Permanently deleted user
    Thanks everyone for your input. Unfortunately we haven't got any closer to understand why the viewer would load up twice in some cases.

     

    There may be 2 separate issues discussed here: 1) slow performance due to map services etc.. 2) viewer loading twice.

     

    To investigate issue 2), I have created a test site on the same Geocortex Essentials instance, to include the same services and applied the same permissions as our main site. I have created a new viewer. No further configuration applied. This viewer does NOT load up twice and takes about half the time, which implies a specific site or viewer configuration may be causing viewer to load up twice.

     

    (Note we are configured site perimissions using Precedence="AllowBeforeDeny" to grant permissions to AD groups.)

     

     

     
    0
  • Permanently deleted user
    This might be something that is easier to troubleshoot with the help of your reseller's support team, but if you've got a simplified site and viewer configuration that uses the same services and permissions and does not load the viewer twice, I would try selectively copying sections of configuration from the older site or viewer to the newer one until you see the same behavior.
    0

Du måste logga in om du vill lämna en kommentar.