rc_aaa_ctx(3)

✨ NAME ✨

okay so bestie, this is rc_aaa_ctx — straight out of the Radius client library, section 3, and it's literally the auth/accounting request builder. No cap. 💖

---

🌈 SYNOPSIS 🌈

#include <radcli/radcli.h>

int rc_aaa_ctx(
    rc_handle        *rh,
    RC_AAA_CTX      **ctx,
    uint32_t          client_port,
    VALUE_PAIR       *send,
    VALUE_PAIR      **received,
    char             *msg,
    int               add_nas_port,
    rc_standard_codes request_type
);

---

🦋 DESCRIPTION 🦋

So like, it builds an authentication/accounting request for port id nas_port with the value_pairs send and submits it to a server. This function keeps its state in ctx after a successful operation. It can be deallocated using rc_aaa_ctx_free(). That's the whole vibe. 🫶

---

🎀 PARAMETERS 🎀

• rh — a handle to parsed configuration. Your config bestie. 💅
• ctx — if non-NULL it will contain the context of the request; its initial value should be NULL and it must be released using rc_aaa_ctx_free(). Do not forget the release, bestie, that's the rule. 🎀
• client_port — the original page literally leaves this one blank, so I'm not inventing lore. It's just client_port, okay? 🙈
• send — a VALUE_PAIR array of values (e.g., PW_USER_NAME). 💖
• received — an allocated array of received values.
• msg — must be an array of PW_MAX_MSG_SIZE or NULL; will contain the concatenation of any PW_REPLY_MESSAGE received.
• add_nas_port — this should be zero; if non-zero it will include PW_NAS_PORT in sent pairs.
• request_type — one of standard RADIUS codes (e.g., PW_ACCESS_REQUEST).

---

🔥 STRUCTURES 🔥

Avoid using this structure directly. Use the rc_avpair_get_ functions.

              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
              };

and bestie, the page literally lists it twice, so here's the exact same warning and struct again, no edits, no cap:

Avoid using this structure directly. Use the rc_avpair_get_ functions.

              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 ⭐

You get the received value_pairs in received, messages from the server in msg, and OK_RC (0) on success. If you get an Access-Challenge, that's CHALLENGE_RC (3). Any failure is negative as the return value. Periodt. 💅

---

🌸 SEE ALSO 🌸

bestie, if you wanna go down the rabbit hole, the page says: 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_aaa_ctx_free(). 💖✨

---

mwah 💋 this page was served by radcli, dated 2023-01-29, and it's all about rc_aaa_ctx(3). bye bestie! 🌈👑