Logins: Older vs New
Folks,
we are holding back our release until we can find an answer to this issue we seem to having now with GE 4.3
In our older (current) setup (GE 4.1.2) the user can close the client/browser down, and our secured sites will challenge the user to log in again. With 4.3 however, it will remember the credentials and log the user straight in!
This maybe fine for personal use, but in an Incident control centre, where multiple people are on shifts etc, we need to track what user is making edits as these are stored in database.
Has something changed at 4.3 that allows this behaviour to happen more readily?
We are using the following URL to login to 4.1.2, and have carried this over to 4.3, if that is an issue even?
http://xxxxxx/geocortex/essentials/rest/security/signIn?app=/gvs/?Viewer=Bushfire&token_type=fragment&idp=AD+AUTHORITY
any thoughts appreciated.
0
-
Got some help for our local support on this one...
We needed to add in a timeout option in the Security Store Editor settings file, in this case 120 seconds.
<ServiceDetails xmlns="clr-namespace:Geocortex.Platform.Security.Integration.IdentityServer">
<GrantLifeSpan>P1D</GrantLifeSpan>
<StateLifeSpan>PT120S</StateLifeSpan>
<DisplayName>Geocortex Identity Server</DisplayName>
<ServiceAddress>http:/xxxxx/Geocortex/IdentityServer</ServiceAddress>
<ServiceName>http://xxxxx.vic.gov.au/geocortex/identityserver</ServiceName>
<ServiceSecret>ZusTrNfpNSeNaJnSd9QtlHVovVqB9Ysud7QYt31+khw=</ServiceSecret>
..
</ServiceDetails>
Each time we close, and then open the browser, we get prompted to login.
To have the application prompt for a login before the page loads, we needed to change our Launch URL, as defined on page 37/38 of the 2.4 Silverlight Admin and development guide.
with the identity server, we use something along the lines of:
http://xxxx/Geocortex/Essentials/REST/security/signIn?token_
type=fragment&idp=urn:gcx:idp:3C5EB560-8251-4718-B91F-CB0CD6F67FCD&app=http://xxxx/gvs/?Viewer=Bushfire0
Please sign in to leave a comment.
Comments
1 comment