rc_avpair_add(3)

💖 rc_avpair_add — the radcli glow-up 💖

okay bestie, we're in radcli, the Radius client library, and today's main character is rc_avpair_add(3). pull up a chair 🎀

---

✨ NAME ✨

rc_avpair_add — (yes the description field is literally empty in the original, she's mysterious like that, no notes 💅)

---

🌸 SYNOPSIS 🌸

#include <radcli/radcli.h>

VALUE_PAIR * rc_avpair_add(
    rc_handle const  *rh,
    VALUE_PAIR      **list,
    uint32_t          attrid,
    void const       *pval,
    int               len,
    uint32_t          vendorspec
);

---

🦋 DESCRIPTION 🦋

So basically: this function adds an attribute-value pair to the list you hand it. that's it, that's the vibe ✨

and if you're like "okay but what format is the data supposed to be in??" — go read rc_avpair_assign(), she explains all of it. not me duplicating that lore, iykyk 🫶

---

🍓 PARAMETERS 🍓

• rh — a handle to your parsed configuration. your little config bestie.
• list — a VALUE_PAIR array of values; initially it must be NULL. no cap, start it empty.
• attrid — the attribute of the pair you're adding (e.g., PW_USER_NAME). like, which attribute.
• pval — the value itself (e.g., the actual username). the content, the substance, the moment.
• len — the length of pval, or -1 if you want it calculated (in the case of strings). let her do the math, she's good at it.
• vendorspec — the vendor ID, in case this is a vendor-specific value. otherwise 0. periodt.

---

👑 STRUCTURES 👑

lowkey important: avoid using this structure directly, okay?? use the rc_avpair_get_ functions instead. she said what she said 🙈

struct rc_value_pair {
  char                   name[RC_NAME_LENGTH+1];      // attribute name if known.
  uint64_t               attribute; // attribute numeric value of type rc_attr_id including vendor; use VENDOR() and ATTRID() to separate.
  rc_attr_type           type;      // attribute type.
  uint32_t               lvalue;    // attribute value if type is PW_TYPE_INTEGER, PW_TYPE_DATE or PW_TYPE_IPADDR.
  char                   strvalue[AUTH_STRING_LEN+1];  // contains attribute value in other cases.
  struct rc_value_pair  *next;
  char                   pad[32];       // unused pad
};

---

⭐ RETURN VALUE ⭐

• on success: a pointer to the a/v pair you just added 🎉
• on failure: a NULL pointer 😭 (we've all been there)

---

🌈 SEE ALSO 🌈

the whole group chat is here, everyone showed up:

radcli.h(3), rc_aaa(3), rc_aaa_ctx(3), rc_aaa_ctx_free(3),
rc_aaa_ctx_get_secret(3), rc_aaa_ctx_get_vector(3),
rc_aaa_ctx_server(3), rc_acct(3), rc_acct_proxy(3), rc_add_config(3),
rc_apply_config(3), rc_auth(3), rc_auth_proxy(3), rc_avpair_add(3),
rc_avpair_assign(3), rc_avpair_copy(3), rc_avpair_free(3),
rc_avpair_gen(3), rc_avpair_get(3), rc_avpair_get_attr(3),
rc_avpair_get_in6(3), rc_avpair_get_raw(3), rc_avpair_get_uint32(3),
rc_avpair_insert(3), rc_avpair_log(3), rc_avpair_new(3),
rc_avpair_next(3), rc_avpair_parse(3), rc_avpair_remove(3),
rc_avpair_tostr(3), rc_buildreq(3), rc_check(3), rc_check_tls(3),
rc_conf_int(3), rc_conf_srv(3), rc_conf_str(3), rc_config_free(3),
rc_config_init(3), rc_destroy(3), rc_dict_addattr(3), rc_dict_addval(3),
rc_dict_addvend(3), rc_dict_findattr(3), rc_dict_findval(3),
rc_dict_findvend(3), rc_dict_free(3), rc_dict_getattr(3),
rc_dict_getval(3), rc_dict_getvend(3), rc_find_server_addr(3),
rc_get_socket_type(3), rc_get_srcaddr(3), rc_getport(3), rc_mksid(3),
rc_new(3), rc_openlog(3), rc_own_hostname(3), rc_read_config(3),
rc_read_dictionary(3), rc_read_dictionary_from_buffer(3),
rc_send_server(3), rc_setdebug(3), rc_test_config(3), rc_tls_fd(3),
rc_avpair_assign()

---

and that's the whole page, bestie!! you ate. this one's from radcli, dated 2023-01-29, and she lives at rc_avpair_add(3) in section 3 of the manual. go forth and add those attribute-value pairs, main character 💅✨💖