Instant Search causes a permissions error

Mark Norbury

17. Mai 2017 20:41

I've just upgraded to Essentials 4.7 (from 4.6) and the GVH 2.8 (from 2.7) and now the Instant Search causes a permissions error.  When I use Instant Search for the first time it works, but then if I use it again it doesn't produce any results and causes other issues: my search workflows no longer work because my user apparently doesn’t have permission, even though these were working before and I did have permission.

 

I have permissions set up in my site so that only Windows authenticated users can access it.  If I remove these permissions, the issue no longer occurs, but we do need these permissions.

 

If I disable Instant Search in my site, then the issue no longer occurs, so this seems to be causing the issue.

 

Has anyone else found something similar?  Is this a bug in Instant Search?

0

• 

  Mark Norbury

  17. Mai 2017 20:43

  One other thing: when I reopen the site it gets stuck in a continuous loop, complaining that I don't have permission to access it, then trying to open it again.

   

  NB. I believe I have set up the redirect URLs correctly.

  0
• 

  Malcolm Walker

  • Community-Manager

  18. Mai 2017 20:24

  Hi Mark,

   

  This is a known issue where you have:

  • Instant Search enabled for one or more layers
  • Permissions set on the Site that would require login, and
  • SSL enabled for the viewer

  The first request for a search is sent through with your sign-in token, since we need to make sure you're allowed to see the layers that you're searching.  There is an internal request made over HTTP to actually perform the search, and an internal policy that invalidates your token if it was generated for an SSL site and then used for a non-SSL site.

   

  Your token, now invalidated, is why you now see permission denied errors for subsequent requests.

   

  For now, we can avoid the issue by disabling the policy that is invalidating your token.  To do so we will need to modify the security store, which will require access to the server.  Please get in contact with Support so we can help you make these modifications.

   

  Regards,

   

  -Malcolm

  0
• 

  Permanently deleted user

  22. Mai 2017 16:24

  I'm having what appears to be the same issue.  I'd like to make the modifications Mark has described but I don't have a maint contract with LG.  Will I need that to contact Support to assist in these changes or is it possible to post the steps here?

  0
• 

  Permanently deleted user

  23. Mai 2017 16:56

  Hi Royce,

   

  Editing the security store can be a little dangerous, so we'd prefer not to post the instructions here.  That being said, please open a support case with us anyways, and we can assist you (Since this is bug related, there will not be a charge for it).  

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  23. Juni 2017 00:51

  Hi Danny,

   

  Is there any ETA for a resolution to this bug?

  0
• 

  Permanently deleted user

  23. Juni 2017 15:52

  Hi Richard,

   

  The target version for this issue is Essentials 4.8.1, but that could change, depending on the other issues that may take precedence.  If you need a hand working around this, please open a support case (you will not be charged for the time).

   

  Thanks!

   

  Danny

  0

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