Are the data protected if they are rendered in backend workflows?

[arthuribeiro]

Currently, I have a backend workflow responsible for generating a 40-character key. I chose this alternative because I need a unique key (composed of numbers and letters) for each user, which cannot be repeated.

In let excludedCharacters, I call all the existing keys in the database to tell the JS not to generate keys identical to them.

However, I’m very concerned about data security. Since I render all the keys in JS, is there any chance that the client can see all the keys of all users, even if it’s done in the backend workflows and called via API Connector?

By the way, if anyone has a better solution for generating unique keys, I’m open to suggestions. Thank you!

[georgecollier]

@arthuribeiro

is there any chance that the client can see all the keys of all users, even if it’s done in the backend workflows and called via API Connector?

No, anything in the backend is hidden, and the only way to get info returned directly from BE workflows is the return data from API action.

[rjwilkinson10]

Regarding alternative ways of creating unique keys, there have been a lot of posts on this that suggest using “calculate random string”. I’m not sure if this will meet your use case exactly but is worth checking out:

Generate random combination of letters and numbers fith fixed length

What I am trying to build is a referral link to our app. I was thinking that I might want to incorporate something personal, like a first name. Or possibly, just the first 3 letters of a name. The name should be pretty easy, just point to the ‘thing’ in the database. What about restricting the length to just 3 letters? Or possibly the first letter of the first name +3 letters of the last + random 5 digit string. Something like: jdoe532X9A4. Sure you can. Remember you can use multiple expre…