You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want apps in different places to be able to use the id service (and the resulting user-api, tracks-api/v3) then we need to say that their origins are trusted. For example, if someone is developing on localhost:8080 they should be able to develop the stream app. Beam faces a similar issue.
Currently what apps are defined in TrustedOrigins is defined cmd/run_server.go. This looks like it's drawing from the config file here. I'm assuming that that config file actually looks different on the server, and that's just for the dev environment.
I see two options:
The easy fix: add localhost:8080 to the config file above.
Harder but possibly more future-proof: limit CORS to be only allowable from the default config above alongside any client host locations stored in the DB.
The text was updated successfully, but these errors were encountered:
If we want apps in different places to be able to use the id service (and the resulting
user-api
,tracks-api/v3
) then we need to say that their origins are trusted. For example, if someone is developing onlocalhost:8080
they should be able to develop the stream app. Beam faces a similar issue.Currently what apps are defined in
TrustedOrigins
is definedcmd/run_server.go
. This looks like it's drawing from the config file here. I'm assuming that that config file actually looks different on the server, and that's just for the dev environment.I see two options:
localhost:8080
to the config file above.The text was updated successfully, but these errors were encountered: