I have an application (full-stack) that is used millions of times concurrently.
Some vital application properties are managed on the client side (at the time it seemed to be the simplest approach to me), but of course this has security issues, so I have to manage all properties on the server side.
I was thinking on adding all these properties to a helper class I have that is
public static. Since the client managed some of these properties I didn't have to worry about whether these properties were the right ones or not since they were per client. If they are on the server side I'm not sure any more how to be certain that the server is using the correct properties for X client.
How can I make sure that the correct properties are being used?
However, putting those properties on the helper class would prompt conflicts, no? Since many clients may access the same property. This would be bad.
The properties in question are to identify the application parameters. i.e. is the application for Photos? Is the application for Personal data? Is the application for my cart? It can be used in many parts of the website so I need to know which part so it can function properly. If I am in photos but it thinks I'm in personal data that is a problem.
I don't manage authentication of clients; it is a library that does that, so that is not an issue.