Trying to understand this from a high level conceptually. It is obvious from all information on Asymmetric encryption that a public key can be of course, public and there isn't a danger of interception. So I'm faced with a point in my software of a key-exchange over server database. An admin user would put out their public key to a public read & write object on my Parse database. The new user requesting to join a group would access this key by a password. The new user then pushes their public key to server and then to admin user. At this point there is a message test sent both ways to ensure the keys are accurate. If they are found to be accurate than all resumes well. If not then a more secure method is employed. All keys are deleted once exchanged of course.
So the main vulnerability with this asymmetric method (from my high level, conceptual knowledge) is that the key could be intercepted and swapped and thereafter sensitive data is being sent ciphered with an attackers key.
The question therefore is: in my situation above, and considering a key verification check, should I still be worried about such an attack?
Additionally and more generally, if there is a message check such as I have outlined above, how could there possibly be a vulnerability of public key swap? ... i.e. if a man in the middle attack occurs, the sent message could not be decrypted by the proper recipient because the attackers public key was used. Therefore both parties would know a key has been compromised and an attack occurred and could act accordingly.