Inherited security credentials
Hello,
We are operating in a DMZ, and we have 3 different Geocortex HTML applications on 3 different servers (we have non-gis application to handle as well).
Our ultimate goal, is to allow people to navigate from one site to the other without having to re-enter credentials, and having their credentials follow them.
The work we have to do now, is to create a portal page (yet a 4th server) that will contain the necessary "things" to authenticate our users.
We are installing an Active Directory and user/roles will be saved there. This means our portal page will use Active Directory to authenticate users.
Now, does anyone have any suggestion as to what mechanism (SQL server session/token, custom token) we should use that would be compatible with how we can manage security with Geocortex?
Of course, we want to take advantage of the security features of Geocortex, and we are not interested in putting a simple door in front of our Geocortex application to let users in or not.
Nothing is set in stone at this time, except the fact users/roles will be stored in the Active Directory.
Any help would be appreciated.
-
Well,
We kinda gave up on Geocortex security.
We found no ways to make Geocortex security swallow the credentials we are getting from our DMZ portal.
Thus being an Active Directory, because we need to have both anonymous access and registered access to the same site, we could not figure out how to make the auto-login to work, hence forcing the registered users to yet, click on the login button.
Hence, we are now ditching the Geocortex security and implementing our own, using HTTP Modules on both, the Geocortex REST API and ESRI's Web Adapter.
That way, we can run both anonymously and registered with the Active Directory, but we lose the nice layer by layer security handling that Geocortex has.
Too bad.
0
Please sign in to leave a comment.
Comments
1 comment