Zum Hauptinhalt gehen

https and secure sites

Permanently deleted user

Hi,

I'm using Geoweb 3.3 and have a problem with secure sites and https. All works fine except the redirect after login.

 

the title bar in IE and Firefox displays the following url.

https://machine/geoweb/web/Login.aspx?ReturnUrl=http://machine.....

The site works fine on https. The login is shown (xml secure) and the user can enter a user name and pass.

If this login is successful the redirect uses a http connection an so fails..

 

Changing the http to https the site will open (still knowing the login information).

Try working with the web.config for internal en external schemes. No difference.

0

Kommentare

10 Kommentare

Datum Stimmen
  • Permanently deleted user

    same error on the timeout page

    function gcxSessionTimeout() {

     

        document.location.href = 'SessionTimeout.aspx?Culture=nl-NL&UICulture=nl-NL&Theme=Geocortex_Essentials&referrer=http%3A
    0
  • Permanently deleted user

    I have an rproxy in the mix so can't replicate your exact scenario.  Did you say you configured the external config via rest manager?

    I don't think this is your issue but you could alter your <add key="EssentialsUrl" value="https://server/Geocortex/Essentials/REST/sites" /> from C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Manager\web.config.

    I presume you will be forcing ALL traffic via a single protocol (e.g. https)??

    Regards

    Brad

    0
  • Permanently deleted user

    Dumb question but can i presume you enabled your site to use SSL under the security tab?

    0
  • Permanently deleted user

    Oh Chris, my bad... Your talking ADF (not REST) aren't you?

    If so, similar question, have you setup the external (rproxy) config or not?

    There is an <add key="internalscheme" value="http"/> in your web.config as part of this config but i'm going to have to have a dig around to remind myself about this.  I'm curious though with what your highlighting however.

    Brad

    0
  • Permanently deleted user

    Hi Brad thanks for your reply.

    Indeed there is some kind of proxy between the IIS and the user. This proxy translates the request from http://machine to https://machine.x.corp. This work perfectly even without settings in the web.config for remote and locale host. I tried almost every setting in the web.config at this time the web.config looks like this:

    <add key="ExternalScheme" value="https"/>

     

        <add key="ExternalHost" value="machine.x.corp"/>

     

        <add key="InternalScheme" value="https"/>

     

        <add key="InternalHost" value="machine.x.corp"/>

     

     

    But this still doesn't help for the redirect. Tried this with only internalhost. Only external. etc etc. Every time restarted IIS in between test. I think the http is hardcoded on two spots the redirect after login and the inactive page.

    even tried <add key="RequireSSL" value="True" />

    0
  • Permanently deleted user

    I've had my test enviro in this state previous but working.  Its now none-ssl since i don't have a valid certificate 2 b working with REST.  My prod again is SSL on both the App Server (ArcGIS Server) & the rproxy.

    A couple of tips:

    - I sometime also bounce the geocortex service as well as the iisreset just to ensure its fully cleared down.

    - if your doing this all internally (which it would appear you are?) then you shouldn't need your external/internal config - comment them all out & see if this makes any difference.

    - Keep EVERYTHING https including your published services from ArcGIS Server (assuming you can do this) although i think underneath you can get away with this.

    I'm a little suspect of what your found hard-coded however so @LATITUDE may need to comment on this.

     

    Brad

     

    0
  • Permanently deleted user

    Thinking about it more Chris, I'm suspect of you setting the external (or internal) config; this is for separate rproxy machine with a separate address as i understand it.  Again, try commenting all of this out.

     

    Brad
    0
  • Permanently deleted user

    Hi Brad,

    Default these are comment out. Went to edit it in the hope it would work. I normally use this when we need a external adress and a working internal adress, but he lets give it a shot.. but nope that didn't help so putting it back in default state.

    I didn't stop and started the geocortex services but i think i would make no difference. I don't say it's hardcoded, but i think it is. But lets see what Latitude will say about this.

    I'm now in the works of making everything https. Setting arcgis output folders to https and now using fiddler/firebug to find that one image that makes IE complain about mixed content :).

    Thanks for your help so far. Any tips on the mixed content to look after (script paths/ css etc) that you know are wrong by default are appreciated,

    0
  • Permanently deleted user

    Chris,

    I'm not certain of what's causing the issue, but I can tell you that the "ExternalScheme" is meant to be used for the login page and the session timeout page, if it is uncommented and configured in the Web.config file.  The AuthenticationManager (configured in the Viewer.aspx page) issues a redirect when login is required:

    Page.Response.Redirect(LoginPage + "?ReturnUrl=" + System.Uri.EscapeDataString(FrameworkUtilities.GetAbsoluteUri()));  

    And the FrameworkUtilities helper class gets the AbsoluteUri value using:

    absoluteUri = String.Format("{0}://{1}{2}", GetScheme(useInternalUri), GetHost(useInternalUri), HttpContext.Current.Request.Url.PathAndQuery);   Which gets the scheme value using:   ConfigurationManager.AppSettings["ExternalScheme"];  

    If the ExternalScheme value is not set in the Web.config file (as is the case for a default Essentials or GeoWeb install), the scheme of the current request will be used instead.  Setting the InternalScheme doesn't affect the scheme in the login page or the session timeout page.  Setting the external host in the Web.config will have an effect on the final URL, but not on the scheme itself.

    My guess is that either the changes to the Web.config are not being picked up (when the ExternalScheme value is uncommented and changed to https), or there is something else happening which is short-circuiting the URL construction, though it's a pretty direct path in the code itself.  The application context *should* automatically reload when a change to the Web.config is made, but the thought that IIS or the application pool should be restarted after the edit deserves some consideration.

    John

    0
  • Permanently deleted user

    John,

    First off nice to here from you again. So you are back in Canada. Missing the Dutch food ? :P

    Secondly thanks for the fast responds.

    The solution you and Brad provided is working now. It seems like the web.config wasn't picked up (like you said). I restarted not only the IIS but also the Geocortex agent. (and been away for a weekend) and now all works. Thanks both for all your help.

     

     

    0

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

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post