If you are here because you encountered this error while trying to authorize an application:
Invalid return_url. Wildcard ("*") allowed origins are no longer supported.
Contact the developer. See https://community.developer.atlassian.com/t/52093
Please contact support for that app and show them this message. If the app is a Trello Power-Up, you can find a Power-Up’s support email by going to the Power-Up’s listing a trello.com/power-ups and looking on the left side bar.
If you’re a Trello application developer, please keep reading.
Notice to Our Developers
Currently, we allow app keys to have pure wildcard allowed origins ("*"). They cannot be added anymore, but if a key had a wildcard origin from before that change was made, the key could continue to use the wildcard origin.
If your key is a legacy app key with a wildcard origin, you should see this message when visiting trello.com/app-key:
On November 4th, we will be fully deprecating wildcard origins, meaning that they will be completely ignored even for legacy app keys. Apps that depend on wildcard origins to complete their auth flow may no longer work. You must remove the wildcard origin and if appropriate, replace it with a real allowed origin of a service you control.
To remove a wildcard allowed origin:
Login to the account of your api key.
Go to trello.com/app-key
Scroll to the Allowed Origin section and delete your wildcard origin.
Note that wildcard subdomains are not affected by this change (e.g. *.atlassian.com).
For information about app key allowed origins, please see our documentation: Authorization
These changes are for app developers. If you’re having issues with an app (such as External Import, or the Trello/Notion integration), please contact support for that app and show them the error you encountered. There’s nothing you can do on your side as a customer to resolve this issue.
Our app is not a legacy app key with a wildcard origin, there’s no such option in the UI. Yet, users are reporting the issue. Given a few reports have come in recently, maybe there’s a problem on the Trello side of things?
Connectors in Power Automate seem to be affected by this change too; which is moving users from Trello to alternatives. Is there any information available that those connectors will be fixed? Or any workaround? Thanks in advance!
I am trying to link the Chrome extension of Taco in with Trello and getting this wildcard error.
I’ve tried removing the extension, updating Chrome etc but always the same.
Looking in the Addon store within Trello and Taco is not there.
New to Trello and trying to add the Trello web part to a SharePoint site but am receiving the error in the original post after clicking “Login” on the O365 connector.
