Windows Authenticated - Secure Site - Fail after Essentials 3.7 Install

Permanently deleted user

February 16, 2012 03:21

I just installed Essentials 3.7 yesterday and I began experiencing trouble with secured sites.  We are using Windows Authentication for the secured sites.  When I try to access the rest end point a login dialog appears, I put in the proper login info but am rejected.  This even happens when I have explicitly added myself to the User Permissions.  SSL is not Required and set as such.  Any suggestions on where to look?

Two points of interest: 

 

  1) Yesterday after I had installed there was no trouble with the Windows Authenticated sites, that started sometime late in the afternoon. 

 

  2) If I access the rest end points on the web server, I do not experience any issues.

Environment:

 

Windows Server 2008 R2 Standard 64 Bit

 

IIS 7.5

Any help is appreciated.

 

Thank You.

0

• 

  Permanently deleted user

  February 16, 2012 05:48

  Louie,

  I'm still at 3.5 & using AD (external provider) as opposed to Windows Authentication but my thoughts on your issues:

  1. Geocortex Agent Config:  Check you've got this right & necessary services are running.  See Page 16/17 of the Geocortex Essentials 3.7.0 Administrator Guide for some background; if however agent service/s are screwed it then your security will also be screwed up.
  2. Your Security Provider Config:  as we use AD (external security provider) we need to run our app pool under a trusted identity; not sure if this applies to you (I'm sure you will remember if it is) but i do know of a bug in the post-installer at 3.5 which will clobber your app pools & set them back to the generic Essential identies.  I found some perhaps relevant sections on page 82 & 95-97 of the Admin guide that could be of interest.

  When you say you have issues, i'm pressuming your trying to access your site via a viewer (presummably Silverlight)?

  Apprecaite the above is pretty geneic but hopefully spark some ideas.

  Brad

  0
• 

  Permanently deleted user

  February 16, 2012 07:37

  Thanx brad.  I really am not sure why but I got it working by changing the EssentialsApp Pool to AppPoolIdentity.

  Louie

  0
• 

  Permanently deleted user

  February 16, 2012 17:27

  Louie, 

   

   

  Glad you got it working.

  When you say AppPoolidentity are you referencing an identity you created?  Typically for AD you need to use an identity that is trusted, such as the local system user 'Network Service' user.

  If your unsure of which identity it should be using for a windows authentication setup, i would be doing a bit more research, perhaps even raise a support call with Latitude to confirm what is required as sometimes its not always clear from the documentation.

  Leave it to you.

   

  Brad

  0

Please sign in to leave a comment.