Incoming message user_id and conversation_id are changing with every request from the same thread

[dkctc-tn]

I use a basic access authentication system on my endpoint using 32 character access codes that are matched first to the user_id and the conversation_id in a db table when a message is received, and if those are not there, then it is a new conversation that needs to be authenticated with an access code.

Now that those values change on every request, I can no longer authenticate without pulling their authentication code out of the message history and checking it every time, and I can no longer track or lock access for access codes to specific users. I can extract potentially matching access codes out of the message history every time, sure, but what good are the user_id and conversation_id if they do not remain consistent between messages?

Is there a solution that allows us to keep track of users and conversations with unique IDs like what we previously had?