# Hosted login page: url parameters no longer work

**URL:** <https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251>\
**Category:** Get Help\
**Tags:** hosted-login-page, lock\
**Created:** [March 21, 2018, 10:21am UTC](https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251 "2018-03-21T10:21:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bartschotten](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@bartschotten](https://community.auth0.com/u/bartschotten)\
**Post date:** [March 21, 2018, 10:21am UTC](https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251/1 "2018-03-21T10:21:46Z")

</div>

We have been using the hosted login page succesfully for a while now. We open the login page from an Android/iOS app and use the respective Auth0.OidcClient (1.0) to pass along some parameters (“extraParameters”).

We have implemented some custom code in the hosted login page that translates the page and adds some branding (colors/logo) based on these parameters.

Yesterday this suddenly stopped working without any changes on our end. First on one Auth0 subscription, and later on our other Auth0 subscription.

The url parameters are no longer getting passed, so they are not available in the login page. As a result our translations/branding is now broken.

I’ve tried with different versions of Lock.js (10.11 and 11.4) and even without any custom code in the hosted login page. The same problem occurs in all situations, on both Android (chrome) and android (safari).

Did you roll-out any changes that could have caused this issue?

Please advice.

---

<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:** [March 21, 2018, 11:38am UTC](https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251/2 "2018-03-21T11:38:16Z")

</div>

The use of extra parameters that are not standard when initiating an OIDC/OAuth 2.0 authentication request is discouraged, however, I did a quick test and a call to `/authorize` that included an additional `x_custom` parameter and required end-user authentication (a redirect to `/login`) still made the `x_custom` parameter available in the hosted login page code through `config.extraParams`.

---

<div class="post-metadata">

**Author:** ![bartschotten](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@bartschotten](https://community.auth0.com/u/bartschotten)\
**Post date:** [March 21, 2018, 12:08pm UTC](https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251/3 "2018-03-21T12:08:24Z")

</div>

Thanks! We were trying to parse the parameters directly from the url, which used to work, but using config.extraParams indeed works fine.

---

<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 22, 2018, 12:08pm UTC](https://community.auth0.com/t/hosted-login-page-url-parameters-no-longer-work/10251/4 "2018-03-22T12:08:28Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
