SASL_AUXPROP_REQUEST(3)
π SASL_AUXPROP_REQUEST π
okay bestie, welcome to the Cyrus SASL corner of the manual, where we talk about asking the library nicely to go fetch you some properties. this is sasl_auxprop_request, and yes it's giving very "let me call in a favor" energy. π«Ά
β¨ SYNOPSIS β¨
#include <sasl/sasl.h>
int sasl_auxprop_request(sasl_conn_t *conn, const char ** propnames)
like, that's the whole vibe. two args. no cap. π
πΈ DESCRIPTION πΈ
int sasl_auxprop_request(sasl_conn_t *conn, const char **propnames)
so here's the tea: sasl_auxprop_request is you literally requesting that the SASL library go obtain properties from any auxiliary property plugins that might be installed. and when we say "might be installed" we mean it β like, for example, the user's home directory from an LDAP server. yes bestie, that kind of property. π
the way this works is so specific and you need to know it: that lookup happens just after username canonicalization is complete. so the timeline matters fr fr β
- make the request before the call to
sasl_server_start(3) - but after the call to
sasl_server_new(3)
that's the window. don't miss it. β°
π¦ Parameters
connβ thesasl_conn_tfor which the request is being made. it's your connection, your main character. πpropnamesβ a NULL-terminated array of property names to request. and listen, this part is important: this array must persist until a call tosasl_dispose(3)on thesasl_conn_t. like, do not let it wander off and get freed. it has to stay. π
π« Returns
Returns SASL_OK on success. that's the slay. for the meanings of other return codes, go check sasl_errors(3) β she explains everything. π
π CONFORMING TO π
RFC 4422 β yes, we're standards-compliant AND cute. iconic behavior. β
π₯ SEE ALSO π₯
sasl(3)sasl_errors(3)sasl_auxprop(3)sasl_auxprop_getctx(3)sasl_server_new(3)sasl_server_start(3)
go read them, bestie. they're all in the group chat. π«Ά
π AUTHOR π
The Cyrus Team. absolute legends, no notes. π
πΈ COPYRIGHT πΈ
1993-2016, The Cyrus Team. π
lowkey reminder:propnameshas to stick around untilsasl_dispose(3). i'm not gonna say it again... okay i might say it again. it's important. π
k bye ily, this has been page SASL_AUXPROP_REQUEST(3) from Cyrus SASL version 2.1.28, dated February 18, 2022 β mwah, slay, periodt. β¨π¦π
π¦ where this page comes from
- alpine 3.22: cyrus-sasl-doc 2.1.28-r8 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- alpine 3.23: cyrus-sasl-doc 2.1.28-r9 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- alpine 3.24: cyrus-sasl-doc 2.1.28-r9 Β· BSD-3-Clause-Attribution AND BSD-4-Clause
- centos-stream 10: cyrus-sasl-devel 2.1.28-27.el10 Β· BSD-Attribution-HPND-disclaimer
- fedora 43: cyrus-sasl-devel 2.1.28-33.fc43 Β· BSD-Attribution-HPND-disclaimer
- fedora 43: cyrus-sasl-devel 2.1.28-33.fc43 Β· BSD-Attribution-HPND-disclaimer
- fedora 44: cyrus-sasl-devel 2.1.28-35.fc44 Β· BSD-Attribution-HPND-disclaimer
- fedora 44: cyrus-sasl-devel 2.1.28-35.fc44 Β· BSD-Attribution-HPND-disclaimer
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-bdb-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- opensuse-leap 16.0: cyrus-sasl-devel 2.1.28-160000.4.1 Β· BSD-4-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms