# Hide Request Parameters of Hosted Login Page

**URL:** <https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846>\
**Category:** Get Help\
**Tags:** hosted-login-page, lock, login\
**Created:** [November 29, 2017, 7:07am UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846 "2017-11-29T07:07:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nosheenzaza](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@nosheenzaza](https://community.auth0.com/u/nosheenzaza)\
**Post date:** [November 29, 2017, 7:07am UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/1 "2017-11-29T07:07:45Z")

</div>

Is there a way use the hosted login page without having to send request parameters using GET? I recently switched from using embedded lock to using the hosted login page in order to be able to call `authorize` with custom audience. All works well, however I am not very happy with the verbose request string.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [November 29, 2017, 6:47pm UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/2 "2017-11-29T18:47:41Z")

</div>

To my knowledge that is currently unavoidable and the request parameters will have to be present in the query component.

---

<div class="post-metadata">

**Author:** ![nosheenzaza](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@nosheenzaza](https://community.auth0.com/u/nosheenzaza)\
**Post date:** [December 4, 2017, 11:45pm UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/3 "2017-12-04T23:45:55Z")

</div>

Ok. The solution would be to wait for the lock widget to support API authorization then.

---

<div class="post-metadata">

**Author:** ![nosheenzaza](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@nosheenzaza](https://community.auth0.com/u/nosheenzaza)\
**Post date:** [December 4, 2017, 11:45pm UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/4 "2017-12-04T23:45:55Z")

</div>

Ok. The solution would be to wait for the lock widget to support API authorization then.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [December 5, 2017, 11:19pm UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/5 "2017-12-05T23:19:37Z")

</div>

Lock 10.22+ supports cross-origin authentication which would allow to do embedded authentication (in the client application itself) while also making an authorization request (aka `audience` parameter). You should check the [cross-origin docs](https://auth0.com/docs/cross-origin-authentication) to see if that would answer your requirements.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/hide-request-parameters-of-hosted-login-page/8846/6 "2018-03-02T05:57:35Z")

</div>


