# HAL API - mountpoint path was overiden by \_scope param

**URL:** <https://community.bloomreach.com/t/hal-api-mountpoint-path-was-overiden-by-scope-param/2914>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [December 10, 2021, 8:40am UTC](https://community.bloomreach.com/t/hal-api-mountpoint-path-was-overiden-by-scope-param/2914 "2021-12-10T08:40:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gnanamoorthi](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@gnanamoorthi](https://community.bloomreach.com/u/gnanamoorthi)\
**Post date:** [December 10, 2021, 8:40am UTC](https://community.bloomreach.com/t/hal-api-mountpoint-path-was-overiden-by-scope-param/2914/1 "2021-12-10T08:40:01Z")

</div>

We have multiple channels and we expect to secure one of the channel.  
Need to restrict channelX at path (/content/documents/channel-x) and channelY as public visible.  
After enabling hal-api, secured channelY was exposed with \_scope param.  
Mountpoint restriction was not working as expected.

Is this intentially done. Can someone help on this.

Ex: [http://localhost:8081/site/halapi/documents?\_scope=/content/documents/channely](http://localhost:8081/site/halapi/documents?_scope=/content/documents/channely)  
expected scenario was is shouldn’t expose this folder documents.

---

<div class="post-metadata">

**Author:** ![jeroen.hoffman](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jeroen.hoffman/32/43_2.png) [@jeroen.hoffman](https://community.bloomreach.com/u/jeroen.hoffman)\
**Post date:** [December 13, 2021, 9:32am UTC](https://community.bloomreach.com/t/hal-api-mountpoint-path-was-overiden-by-scope-param/2914/2 "2021-12-13T09:32:29Z")

</div>

Hi,  
How exactly did you secure channel Y, by hst:authenticated config I guess?

HAL doesn’t look at that, it looks just directly at the content.  
You could override GenericHalApiDocsResource#getScopeNode are do a Spring reconfiguration to get your customization in. Or protect the content by security domains, probably need changing the user session for HAL too.

HTH  
Jeroen

---

<div class="post-metadata">

**Author:** ![gnanamoorthi](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@gnanamoorthi](https://community.bloomreach.com/u/gnanamoorthi)\
**Post date:** [December 22, 2021, 7:21am UTC](https://community.bloomreach.com/t/hal-api-mountpoint-path-was-overiden-by-scope-param/2914/3 "2021-12-22T07:21:42Z")

</div>

Hi Jeroen,

Thanks, we restricted by customizing valve implementation approach.

With this approach we can’t return JSON response based on Custom Exception/ WebApplicationException. It gives only ContainerException rather than WebApplicationExceptionMapper impl.
