#@graphql
13 messages · Page 1 of 1 (latest)
yes, you are correct, but I would like it to be overshadowed like everything else, because the company has a security test and they complained about this situation
I wanted to at least make graphql more difficult to visualize
idk much about graphql and i am not a security expert. But I think the only reasonable thing to do is use UUID instead of incremental IDs.
if you hide the query in your code it will be still visible in the network requests, no?
or maybe I am wrong because I don't understand graphql
the problem here is not the "payload", here the problem is that the bad person knows the graphql structure
They can always inspect the network tab ?
Anyway, you said you are trying it, but you can't. What are you trying that isnt working?
on the network there is a library that obfuscates the request, the problem is that you can see the structure in the js files
anyway the security team won't let this problem go 😄
Well, I was curious what you tried and what isnt working.
Mostly to avoid sharing the obvious, but anyway: https://github.com/javascript-obfuscator/javascript-obfuscator/issues/696
i also tried this library