'Invalid Portal Url' during Post-Installtion of 4.3.1
Hi to all
just curious if anyone else has had this message while trying out the use of ArcGIS Online for the Sign-In Options.
I get this message both with the ArcGIS Online url and the organisation specific option.
There is a comment in the release notes for version 4.3.0:
GE-5109: “Invalid Portal URL” error message can obscure more informative error messages related to HTTP communication
What was done to stop obscuring helpful messages is not entirely clear however.
It is possible that the user that the Post-Installer application runs as done not have appropriate permisions to get through the network proxy to the ArcGIS Online servers.
If that is the case does anyone know how to change it or to be able to configure proxy permissions in a config file for it.?
Looking forward to your thoughts
Regards
Ralph Price
-
Hi Ralph,
The error text now has a tooltip that contains the underlying error message. The full error details will also be written to the Post Installer log.
Yes, this could be a proxy issue. If you have had to configure proxies for the REST and Manager applications then you will need to do the same in the Geocortex.Essentials.PostInstall.exe.config file right next to the Post Installer executable. See https://msdn.microsoft.com/en-us/library/kd3cf2ex(v=vs.110).aspx.
--Ryan
0 -
Thanks Ryan
thanks for that pointer.
Adding in the following into the configuration element worked to the point of accepting the URL:
<system.net>
<defaultProxy
useDefaultCredentials="true"
enabled="true"
>
<proxy
usesystemdefault="true"
proxyaddress="http://proxyServerName:Port"
bypassonlocal="true"
/>
</defaultProxy>
</system.net>I believe that this method of security should only work if the ArcGIS Online account that is used has Admin level rights in the Organisational account (pg 57) of the GE Installation Guide.
Do you know what reaction the Geocortex Manager should give when a user that does not have ArcGIS Online Admin rights (ie my own account) tries to log in to the Geocortex Essentials Manager ?
I get a page with this url:
which displays this message:
/customer/servlet/servlet.FileDownload?file=00P6000000em1RgEAI
Clicking the Return to Application returns to this login screen:
/customer/servlet/servlet.FileDownload?file=00P6000000eltitEAA
Unfortunately the Admin user here is away for the day. I will get him to try tomorrow to see what difference I get and or upgrade my priivileges for this purpose.
Has anyone tried using Custom Permissions in ArcGIS Online for this as compared to full admin permissions?
Regards
Ralph Price
0 -
Hi Ralph,
This sounds like Manager is failing when it attempts to make a request to ArcGIS Online to fetch user information. Both Manager and REST web applications will likely need the same proxy configuration in their web.config that the Post Installer has. Check the Manager logs to see if there are error details.
By default the administrators of your ArcGIS Online organization will be able to sign in to Manager as well as the ArcGIS Online user account you used when the Post Installer prompted you for ArcGIS Online credentials.
--Ryan
0 -
Hi Ryan
I haven't previously needed to do any proxy configurations. Our GE sites and AGS map services that we make publically available are behind a reverse proxy (Microsoft's Threat Management Gateway).
As to the other config files, I assume that you mean these two:
- GE Manager - C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Manager\Web.config
- GE REST - C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\Web.config
I have added the following to those files:
/customer/servlet/servlet.FileDownload?file=00P6000000em1KuEAI
and unfortunately ending up with the same apparent error.
There does not appear to be any apparent error as far as Fiddler is concerned:
/customer/servlet/servlet.FileDownload?file=00P6000000elu3EEAQ
Any thoughts would be appreciated
Regards
Ralph Price
0 -
Hi Ralph,
Those are indeed the web.configs I was referring to.
Perhaps your app pool accounts do not have permission to talk to the proxy. There are HTTP 407 responses in Fiddler which indicates that the proxy requires authentication.
--Ryan
0 -
Thanks Ryan
I will follow that avenue
Regards
Ralph
0
Please sign in to leave a comment.
Comments
6 comments