9 Aug
2018
9 Aug
'18
8:46 a.m.
On Aug 8, 2018, at 5:12 PM, Kevin Virk <Kevin.Virk@faithlife.com> wrote:
figured it out I had not included the line require-message-authentication=no in my clients.conf. Thank you for your help Alan!
That wasn't the problem. "Invalid request authenticator" means that the shared secret is wrong. If you had set "request_message_authenticator = yes", then the message would have been "invalid message authenticator", or maybe "missing message authenticator" What I suspect happened is that you were editing clients.conf, and then *not* restarting the server. After changing "require_message_authenticator = no" and restarting the server, it picked up the new secret. Alan DeKok.