How about using it for app configuration and everyone reads it with the same ID?
EG: Instead of username/id, you use ONE ID for the app, (User:MyBusinessApp@abc.com), base-BusApp and all users ONLY retrieve data, That way I can hold the App config in this table and retrieve it as needed.
I would then have an ‘admin’ user update (with another app) that updates this table. This would be the app owner only who updates the config.
Adding a quick flow for clarity. A quick powerpoint flow
Good idea/Bad idea?
I would hate to go too far down the path to find its a bad idea!
Pros:
Easy config retrieval in the app.
Hosted config allows for online updates
Can cache the results and pull new config if we update the version#
I could write user prefs out to a different ID if I want.
Cons:
If hacking the app exposes the ID/PW, is it really a concern? It will be read only for the released app. The editor app will be a desktop app.
This sounds like a reasonable plan to me as long as the server is HTTPS.
Sure, it’s not 100% secure, but it isn’t terrible.
You can further secure it by encrypting or obfuscating any data you save in the table. This will further help protect it when it goes over the wire and on the server.
Whether the connection is secure (HTTPS) or in the clear (HTTP) totally makes a difference.
I’m unclear why the port is important. Anyone who wants to scan the local area network for in the clear traffic your customers are using would easily capture data sent on any port.
I did look at the HTTPS, and did note that it failed. I took a look at the droplet, but this is somewhat out of my league.I’ll look forward to seeing a solution for that one
(This is a basic substitution-cipher encode/decode module).
OR -
One can use one of the libraries provided w/ Corona (or plugins) to encrypt/decrypt data. However, once you do this, you need to mark your app as using encryption tech. My substitution-cipher module is the middle ground since it isn’t technically encryption.
Curious, can I use SSK to obfuscate my data and then use SSK to obfuscate the key for the original obfuscation? In other words, if I make a chain of keys, each obscured by your substitution-cipher module, would I be doing anything substantial or just making myself feel better?
@roaminggamer What about saving the key to your keychain using the new Keychain plugin? Your key would then be secure in a format native to your device so it would avoid tagging your app as an encrypted data user.
This sounds like a reasonable plan to me as long as the server is HTTPS.
Sure, it’s not 100% secure, but it isn’t terrible.
You can further secure it by encrypting or obfuscating any data you save in the table. This will further help protect it when it goes over the wire and on the server.
Whether the connection is secure (HTTPS) or in the clear (HTTP) totally makes a difference.
I’m unclear why the port is important. Anyone who wants to scan the local area network for in the clear traffic your customers are using would easily capture data sent on any port.
