Issues using identify w/ buffer on Windows Authenticated service

Permanently deleted user

30. Mai 2018 17:23

Has anyone else run into the following issue with the identify tool and it's associated buffering menu flyout in GVH 2.6.1 / Essentials 4.5.1?

 

I added a windows authenticated service (with multiple layers in it) to a site and added the identify tool and IdentifyToolControlRegion widget to my menu - so far so good.

 

If I use the identify tool without buffering the request completes successfully, meaning it passed the required authentication along with the query request.  However, if I enable buffering, the buffer request will complete fine but the identify requests fail with a 401 Unauthorized error.  The requests are identical except in the buffered request, the client does not send an authentication header.

 

Any ideas/solutions/workarounds greatly appreciated.

0

• 

  James Brink

  31. Mai 2018 12:14

  Peter

   

  We got the same problem and reported it in 2016 (Case Number: 00078676).

   

  What is your Geometry service? Are you using the ESRI geometry service? Your own geometry service?

   

  We proxy our map services and our geometry service wasn't getting proxied, all other services proxied. GeoCortex helped us add a proxy rule to our index.html where it would add a proxy to any service that wasn't proxied.

  0
• 

  Permanently deleted user

  31. Mai 2018 13:23

  @Jimmy,

   

  We use our own geometry service and that part is working okay - the buffer request does not get proxied and it returns a valid json object to the client app.  The problem seems to be with the query request (next step after buffering) which returns a 401 error.  When I looked closer at the requests in the dev console yesterday it actually appears that the request is sent multiple times - first with no authentication header, then with a couple different auth header strings - the last one seems to work (returns http 200 response) but the client still says there was a problem and doesn't show the results.  The same request, however, will work flawlessly if we don't buffer it.

   

  We removed all proxy configurations because the default proxy will not pass any windows authentication credentials.

  0

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