api-key

Security of Mobile Backend API key

核能气质少年 提交于 2020-06-15 21:27:55
问题 Suppose I am developing a mobile application that makes calls to an API server. The API server is secured by an API Key. I cannot hard-code the API Key inside the mobile application because it can be stolen. How can I protect the API key? 回答1: How is that problem usually solved? (It sounds like the API-key you are trying to protect is for an API service that you don't own.) One approach is by using an authentication server. The private API-key is kept on the authentication server and only

Security of Mobile Backend API key

馋奶兔 提交于 2020-06-15 21:26:15
问题 Suppose I am developing a mobile application that makes calls to an API server. The API server is secured by an API Key. I cannot hard-code the API Key inside the mobile application because it can be stolen. How can I protect the API key? 回答1: How is that problem usually solved? (It sounds like the API-key you are trying to protect is for an API service that you don't own.) One approach is by using an authentication server. The private API-key is kept on the authentication server and only

Security of Mobile Backend API key

余生长醉 提交于 2020-06-15 21:25:46
问题 Suppose I am developing a mobile application that makes calls to an API server. The API server is secured by an API Key. I cannot hard-code the API Key inside the mobile application because it can be stolen. How can I protect the API key? 回答1: How is that problem usually solved? (It sounds like the API-key you are trying to protect is for an API service that you don't own.) One approach is by using an authentication server. The private API-key is kept on the authentication server and only

Should I hide firebase api keys into backend? Not due to data security but project cloning issue

泪湿孤枕 提交于 2020-06-09 19:49:29
问题 Can someone help me with firebase security questions? Here's what I was try to figure out: I understand that to let a client side interacting with my firebase app, a config and firebase.initializeApp(config) will be exposed to public, and everyone using the client side can see it in browser developer console. I also know that this is fine because I can use security rules and auth to secure data. But, if someone copied all my client code (including configs) and build a lot of cloned sites,

Should I hide firebase api keys into backend? Not due to data security but project cloning issue

牧云@^-^@ 提交于 2020-06-09 19:46:31
问题 Can someone help me with firebase security questions? Here's what I was try to figure out: I understand that to let a client side interacting with my firebase app, a config and firebase.initializeApp(config) will be exposed to public, and everyone using the client side can see it in browser developer console. I also know that this is fine because I can use security rules and auth to secure data. But, if someone copied all my client code (including configs) and build a lot of cloned sites,

Should I hide firebase api keys into backend? Not due to data security but project cloning issue

℡╲_俬逩灬. 提交于 2020-06-09 19:46:30
问题 Can someone help me with firebase security questions? Here's what I was try to figure out: I understand that to let a client side interacting with my firebase app, a config and firebase.initializeApp(config) will be exposed to public, and everyone using the client side can see it in browser developer console. I also know that this is fine because I can use security rules and auth to secure data. But, if someone copied all my client code (including configs) and build a lot of cloned sites,