Support Forums

Limitations of app_metadata and user_metadata content in identity-signup

Hello, I’ve recently ran into issue while using identity-signup function. I’ve debugged a bit, and like to ask if there are some new limitations or requirements on app_metadata and user_metadata content.

I’ve been sending sending string of approximate length of 500 characters, composed of unicode characters. Until recently everything worked as expected, but few weeks ago, netlify identity started to ignore whole added content of both app_metadata and user_metadata (even other keys like “role”) and worked only without the aforementioned string of if it was shortened to several characters only.

Is there some limit of metadata size for indentity signup function?

Hey there, @Ondrej_Marik :wave:

Thanks so much for your patience. I want to confirm we haven’t forgotten about this thread! We are in the process of getting the relevant information you need and will follow up on this thread as soon as we have more insights. Thanks again!

Hey @Ondrej_Marik,

Apologies for the delay in getting back to you. But to answer your question, theoretically there are no limits on the amount of data that can be stored in Identity objects. However, most browsers have a limit of 4096 bytes for a cookie. Since a JWT contains all this data in base64 format in the cookie itself, it’s probably easy to hit that limit with too many characters or information. So it’s best to keep it to a minimum.