MEMCACHED_S...T_AUTH_DATA(3)

💖 MEMCACHED_S...T_AUTH_DATA 💖

okay bestie, gather round, because we're talking about libmemcached-awesome and its SASL auth data situation, and honestly? it's giving "powerful but you gotta read the fine print" 🎀

---

✨ NAME ✨

memcached_sasl_set_auth_data — the libmemcached documentation, but make it make sense 🦋

---

🌸 SYNOPSIS 🌸

#include <libmemcached/memcached.h>

and like, obviously:

Compile and link with -lmemcached

here come the functions, bestie:

void memcached_set_sasl_callbacks(memcached_st *ptr, const sasl_callback_t *callbacks)

Parameters

• ptr — pointer to initialized memcached_st struct
• callbacks — pointer to sasl_callbacks_t holding the callbacks to use

const sasl_callback_t *memcached_get_sasl_callbacks(memcached_st *ptr)

Parameters

• ptr — pointer to initialized memcached_st struct

Returns

• pointer to sasl_callbacks_t holding the callbacks currently used

memcached_return_t memcached_set_sasl_auth_data(memcached_st *ptr, const char *username, const char *password)

Parameters

• ptr — pointer to initialized memcached_st struct
• username — (it's literally just... the username, no notes 📝)
• password — (and the password, iconic)

Returns

• memcached_return_t indicating success

memcached_return_t memcached_destroy_sasl_auth_data(memcached_st *ptr)

Parameters

• ptr — pointer to initialized memcached_st struct

Returns

• memcached_return_t indicating success

---

💅 DESCRIPTION 💅

libmemcached lets you plug in your very own callbacks function, the kind that libsasl uses to do SASL authentication. main character energy, honestly 💖

⚠️ please note: SASL requires the memcached binary protocol, and you have to specify the callbacks before you connect to the server. no cap, do it in that order or it's not gonna work 😭

memcached_set_sasl_auth_data() is the lil helper function that defines the basic functionality for you, but heads up bestie — it will store the username and password in memory. 🙈

If you choose to use this method, you have to call memcached_destroy_sasl_auth_data() before calling memcached_free() to avoid a memory leak. do not skip this step, the leak is real and it's messy 🫶

And also — and this is the part where people get it wrong — you should NOT call memcached_destroy_sasl_auth_data() if you specify your own callback function with memcached_set_sasl_callbacks(). like, don't do it. just don't. ✋

---

🌈 RETURN VALUE 🌈

• memcached_get_sasl_callbacks() returns the callbacks currently used by this memcached handle. 👑
• memcached_set_sasl_auth_data() returns MEMCACHED_SUCCESS upon success. slay ✨

---

🦋 SEE ALSO 🦋

• memcached(1)
• libmemcached(3)
• memcached_strerror(3)
• sasl_client_new(3)
• sasl_callbacks(3)

---

and that's the whole vibe, bestie — this was libmemcached-awesome version 1.1, dated Jul 24, 2025, brought to you by the MEMCACHED_S...T_AUTH_DATA(3) girlies. go forth, authenticate responsibly, and don't leak that memory 💖✨🎀🦋🌸💅