1

I created app with react and express (client-side rendering). I use react-stormpath. When I added https://my-app-name.herokuapp.com into Authorized Origin URIs in Stormpath Admin it works ok. But when I created pipeline with review apps, it created new subdomain with every request e.g. https://my-app-name-pr-1.herokuapp.com and there is problem with CORS, because this new url is not in Authorized Origin URIs. And I can't use wildcards like: https://*.herokuapp.com.

Some hints how to manage it? Because I really don't want to add new Authorized Origin on every pull request.

Really thanks!

Improve this question

1 Answer 1

Reset to default
1

The inability to use wildcards for the Authorized Origin URIs is a bug that we are fixing, the fix should go out soon. If you need to work around this issue ASAP you can use one of our SDKs (like the Stormpath Node SDK) to programmatically add URLs the the application.

Improve this answer
3
  • Really thanks for soo fast answer! This issue is not urgent, so I will wait for release. Do you plan something like reg-ex for uri in the future? I mean for example: my-app-pr-[1-9].herokuapp.com, because *.herokuapp.com allow access to all herokuapp-developers.
    – Adam Ryvola
    Commented Jan 26, 2017 at 19:24
  • No prob! Today's release just went live, and it appears that the wildcards are now working, can you confirm that it's working for you as well? Regarding the regex request, that's a good idea, would you mind adding that to ideas.stormpath.com - thanks!
    – robertjd
    Commented Jan 26, 2017 at 19:51
  • Sure, I will test it and give you feedback. And I will add issue about reg-ex to ideas too.
    – Adam Ryvola
    Commented Jan 27, 2017 at 8:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.