You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building a mobile application that spawns a docker container running a daemon which accepts rpc commands. I have been looking at WAMP as a way to route a daemon rpc call generated by the mobile client through the WAMP router to their daemon. For testing I have done this easily by just passing rpc creds as parameters in the WAMP procedure. I am pretty positive this is an awful idea but I don't know why and if it is an awful idea as I suspect is it possible to do it better?
I don't have enough background on the problem, but you can use an authentication mechanism to verify a client's permissions upon connection establishment. See the documentation website.
I guess you should minimize the number of times you pass these on the wire.
Authenticate first using HTTPS and receive a cookie. Then use cookie based
authentication. Use WAMP over wss.
Maybe others have more concrete input.
Elad
Activity
darkl commentedon May 16, 2020
I don't have enough background on the problem, but you can use an authentication mechanism to verify a client's permissions upon connection establishment. See the documentation website.
Dinglebarry9 commentedon May 16, 2020
The credential are just a username and password, what I am asking is should I also encrypt the parameters that I pass?
darkl commentedon May 16, 2020
darkl commentedon May 16, 2020
Here, read this.
Dinglebarry9 commentedon May 16, 2020
Thank you I will check this out.