we have a single page app that we’re building, and we’re having an issue getting the {organization_name} placeholder in the allowed callbacks to work. from what I can tell in the documentation we aren’t doing anything wrong - the url is listed in the application config as https://{organization_name}.dev.ourdomain.com (changed the actual domain for privacy)
when we try to login through an organization specific domain, IE https://testorg.dev.ourdomain.com we get an error saying ‘The provided redirect_uri is not in the list of allowed callback URLs.’
We have the app configured to allow both personal and organization logins, and I double checked that we’re using the correct name of one of our registered organizations, and we are. Also, if I change the application config to use the * wildcard instead https://*.dev.ourdomain.com everything works fine.
Am I misunderstanding how to use the organization_name placeholder?
I found a few topics similar to this one, but no answers for this particular issue
@sumansaurav yes, I’ve read that document and did my best to make sure we were following its rules.
my understanding is that https://{organization_name}.dev.ourdomain.com should be a valid entry, and that if we have an organization with a name of ‘testorg’ our app should allow callbacks to https://testorg.dev.ourdomain.com right?
Can you also check and let me know if organization placeholder and wildcard present in same configuration? If yes, you should only be using organization place holder not wildcard in same configuration.
no, we only have the one url with the place holder. We do have other variations of that domain in the list, as well as entries for localhost, but none of them are using any placeholders or wildcards.
I’ve read through this thread and have reached out internally to confirm expected behavior with organization_name in the Allowed Callback URLs field. I will keep you updated.
I confirmed with product manager that the URL of https://testorg.dev.ourdomain.com should work as it follows all rules listed here: Organization URL Placeholders
They recommended I open a up a ticket to the Engineering team for them to take a closer look at why this is not working for you. I will need a bit more information from you before I can do that. Can you kindly DM me the tenant name where you are implementing this, any relevant code/URL snippets, and capture a few screenshots showing the error?
Hi @marybeth.hunter! We actually noticed that param key was wrong just a couple hours ago because of a completely unrelated issue! Unfortunately I have no control over the UI code that’s having the issue, but our UI team has a fix that should get deployed soon. once it is, I’ll change our auth0 config and test.
Will report back when I have results!
Thanks,
Josh
