Reputation: 671
sso.com
, one central site for sign-on, with a CORS-enabled APIstatic1.org
, static2.net
.sso.com
.sso.com
.I am unable to find any examples of this scenario being done in practice. Is that because it's actually a security problem? Would we need to be very careful about the approved list of CORS domains?
Upvotes: 2
Views: 146
Reputation: 7165
This sounds like how data is served to big websites (Facebook, Google, etc).
As far as security goes, as long as you are authenticating server-side, and making sure that crucial account actions (saving things to the database, altering the database etc etc) are done server-side, then you should be perfectly safe in doing this.
The key here is just making sure that sensitive data is handled by the server and not the client. If you keep that in mind, you can build the application with security in mind. Also, never trust user input.
I hope this helps!
Upvotes: 1