MONGOC_OIDC_C...WITH_USER_DATA(3)

📦
version 2.5.6 · 3 versions
, in epel 10

🎀 MONGOC_OIDC_C...WITH_USER_DATA(3) 🎀

okay so bestie, this one's a page from libmongoc (that's the MongoDB C driver, mwah) and it's the whole tea on mongoc_oidc_callback_new_with_user_data 💅. It's a lil constructor function, it's giving "build me a callback wrapper" and honestly? iconic behavior.

✨ SYNOPSIS ✨

mongoc_oidc_callback_t *
mongoc_oidc_callback_new_with_user_data (mongoc_oidc_callback_fn_t fn, void *user_data)

So what it does is make you a brand-new mongoc_oidc_callback_t object, and that object stores two things: the OIDC callback function you hand it, and a pointer to your user data. Literally just wrapping them up together like a little gift 🎁.

⚠️ WARNING, and I mean it fr fr: the lifetime of the object that user_data points to? That's on you, the user — it is NOT managed by the mongoc_oidc_callback_t! Like, mongoc is not gonna babysit it, it is not gonna free it for you, that pointer is your responsibility, no cap. 🫶

🌸 PARAMETERS 🌸

  • fn — a mongoc_oidc_callback_fn_t. Must not be NULL. (It's mandatory, bestie, non-negotiable 💀)
  • user_data — a pointer to your user data, or NULL. Either one is valid here, so no pressure ✨

💖 RETURNS 💖

You get back a shiny new mongoc_oidc_callback_t that you must free with mongoc_oidc_callback_destroy(). Or, if you gave it an invalid argument, you get NULL — so like, do check that, okay? 🙈

🦋 SEE ALSO 🦋

  • mongoc_oidc_callback_t
  • mongoc_oidc_callback_new()

(yes, there's a non-user-data version too, go treat yourself, read both 👑)

🌈 AUTHOR 🌈

MongoDB, Inc. — the whole entire company, slaying as always 💜

2009-present, MongoDB, Inc. — periodt.

and that's the whole page, bestie! this era of the docs is libmongoc version 2.5.6, dated Oct 09, 2026 — screenshot it, cite it, live ur truth 🧚💖✨

📦 where this page comes from