# Can I use wildcards in redirect\_uri after login?

**URL:** <https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [February 5, 2024, 1:56pm UTC](https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523 "2024-02-05T13:56:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [February 5, 2024, 1:56pm UTC](https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523/1 "2024-02-05T13:56:36Z")

</div>

Hey everyone,

I have the following front-end code that handles my login with the universal login.

```auto
export const auth0Client = createAuth0Client({
	domain: config.auth.domain,
	clientId: config.auth.clientId,
	cacheLocation: 'localstorage',
	authorizationParams: {
		redirect_uri: window.location.origin,
		audience: config.auth.audience
	}
})

```

What I’d like to do is to add a deeper URI to `redirect_uri: window.location.origin` so I can bounce my user to the deep link they requested. However this seems to require specifying each and every possible valid URI in the Auth0 back-end.

Is there any simple way round this?

Many thanks!

---

<div class="post-metadata">

**Author:** ![marcelina.barycka](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/marcelina.barycka/32/56162_2.png) [@marcelina.barycka](https://community.auth0.com/u/marcelina.barycka)\
**Post date:** [February 5, 2024, 3:11pm UTC](https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523/2 "2024-02-05T15:11:19Z")

</div>

Hey @kkrp1 , thanks for posting.

> [@kkrp1](#):
>
> However this seems to require specifying each and every possible valid URI in the Auth0 back-end.

If I’m not mistaken, under the Allowed Calback URLs in your Auth0 tenant, you can add wildcard for the subdomain, like `https://*.example.com`, but not this way `https://example.com/*`

This docs can be also useful to review - [How do I set up a dynamic Allowed Callback URL?](https://community.auth0.com/t/how-do-i-set-up-a-dynamic-allowed-callback-url/60268)

Please let me know if you have any follow up questions!

---

<div class="post-metadata">

**Author:** ![kkrp1](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kkrp1](https://community.auth0.com/u/kkrp1)\
**Post date:** [February 6, 2024, 12:50pm UTC](https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523/3 "2024-02-06T12:50:32Z")

</div>

Thank you. It was really the latter (wildcards in URI) I was after, but if that’s not possible, then the state solution outlined in the linked docs would seem to be the way to go.

Appreciate the help.

---

<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:** [February 20, 2024, 1:01pm UTC](https://community.auth0.com/t/can-i-use-wildcards-in-redirect-uri-after-login/126523/5 "2024-02-20T13:01:00Z")

</div>

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