# Search secured/tokenized or something?

**URL:** https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382
**Category:** Automation
**Created:** [October 28, 2019, 7:21pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382 "2019-10-28T19:21:38Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![understandit](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/u/22d042/32.png) [@understandit](https://discourse.devontechnologies.com/u/understandit)
#### Post date: [October 28, 2019, 7:21pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/1 "2019-10-28T19:21:38Z")

</div>

I tried to create a plugin based on the instructions, but when I follow the instructions and copy and paste the URL, I get this after the domain name:  
/app/secure/ocl/lrs/do/advSrch?V\_SEARCH.command=navigate&V\_TOKEN=1234567890&V\_SEARCH.docsStart=50  
I don’t see how I can edit this URL as per the instructions. Options?

---

<div class="post-metadata">

### Author: ![cgrunenberg](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/cgrunenberg/32/7172_2.png) [@cgrunenberg](https://discourse.devontechnologies.com/u/cgrunenberg)
#### Post date: [October 30, 2019, 1:21pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/2 "2019-10-30T13:21:37Z")

</div>

Could you please post the complete plugin? Thanks.

---

<div class="post-metadata">

### Author: ![understandit](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/u/22d042/32.png) [@understandit](https://discourse.devontechnologies.com/u/understandit)
#### Post date: [October 30, 2019, 1:47pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/3 "2019-10-30T13:47:00Z")

</div>

I must apologize, because I’m not sure, really, what exactly you are asking me. I was trying to create a plug-in. I have low experience doing it (though did find some instances where it was simple to do following the instructions in the DevonThink manual and delighted with the results). But the URL captured/copied using the documented method yielded the string I provided.  
I presume you are looking for the address at the beginning of the string: lobbycanada.gc.ca  
When I tried to provide the complete URL the security on your system would not accept the entry.

---

<div class="post-metadata">

### Author: ![cgrunenberg](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/cgrunenberg/32/7172_2.png) [@cgrunenberg](https://discourse.devontechnologies.com/u/cgrunenberg)
#### Post date: [October 30, 2019, 1:50pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/4 "2019-10-30T13:50:25Z")

</div>

In this case the assistant is not able to automatically generate a useful plugin as the URL doesn’t include a search term.

---

<div class="post-metadata">

### Author: ![understandit](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/u/22d042/32.png) [@understandit](https://discourse.devontechnologies.com/u/understandit)
#### Post date: [October 30, 2019, 3:00pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/5 "2019-10-30T15:00:00Z")

</div>

I’ve been running into a few search pages that seem to be set up like this, particularly on government sites. I’m open to ideas from anyone on best practices for automating searches in these instances. Feels like a move is on to keep searches from coming under attack by bots, though?  
Are we headed for a world of ‘register to search’ I wonder?  
Thanks for your input, to keep me from barking up a tree with no cat. 😉

---

<div class="post-metadata">

### Author: ![cgrunenberg](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/cgrunenberg/32/7172_2.png) [@cgrunenberg](https://discourse.devontechnologies.com/u/cgrunenberg)
#### Post date: [October 30, 2019, 3:03pm UTC](https://discourse.devontechnologies.com/t/search-secured-tokenized-or-something/51382/6 "2019-10-30T15:03:10Z")

</div>

> [@understandit](#):
>
> I’m open to ideas from anyone on best practices for automating searches in these instances. Feels like a move is on to keep searches from coming under attack by bots, though?  
> Are we headed for a world of ‘register to search’ I wonder?  
> Thanks for your input, to keep me from barking up a tree with no cat. 😉

It might be possible but is usually quite complicated and specific for every website as the HTML code has to be examined to figure out the necessary HTTP post.
