https://www.growthbook.io/ logo
Join Slack
Powered by
hello again :wave: i'm playing around more with th...
# sdk-react
e
hello again 👋 i'm playing around more with the sample nextjs app, and was trying out the hybrid route. it mentions to 
getDecryptedPayload
to make sure we can make the initial client side render synchronous
r
Hi! Saw your other messages, too, but was there something specific about ​`getDecryptedPayload`​ that you wanted to know?
e
well, i'm writing an RFC, and we're using nextjs. I think ideally we don't want to show the actual flags and values on the client, but wan to pass the values like in the hybrid example.
so I set up an encrypted sdk connection
but realized I need the 
premium
features to actually test things out.
but if it was passed encrypted, sounds like we'd need to 
await
the init or something, right?
and well, use init instead of initSync.
r
You're right that you need to use async ​`init`​ with encrypted payloads. But, your overall goal is to use the hybrid rendering strategy but retain encrypted payloads on the client. Is that right?
e
yes, ideally
r
Thanks. Following up with the team and will get back to you.
Hi. The short answer here is that it's not possible with Next's current architecture. For entirely secure data in hybrid rendering, you'd need to do everything on the server or use remote evaluation. That being said, one of our engineers did mention that in the hybrid, the data that's passed from the server to the client isn't easily accessed (it's not like a the response from a network call, e.g.). So, depending on your requirements, it may be enough obfuscation.
e
yeah, I saw where it is at
it may be enough, trying to be thorough in my evaluation
was a question from one of our folks.
👍 1
35 Views
Open in Slack
PreviousNext
Powered by