SASL_USER_EXISTS(3)
π sasl_user_exists β bestie edition β¨
okay so real talk, this is sasl_user_exists(3), one of the little cuties from the Cyrus SASL manual (section 3, we're in library-call territory, very demure, very coder girl π
).
πΈ NAME πΈ
sasl_user_exists β Cyrus SASL documentation π«Ά
β¨ SYNOPSIS β¨
no cap, here's the vibe, copy it exactly:
#include <sasl/sasl.h>
int sasl_user_exists( sasl_conn_t *conn,
const char *service,
const char *user_realm,
const char *user)
π¦ DESCRIPTION π¦
same signature, one more time because she's iconic:
int sasl_user_exists( sasl_conn_t *conn,
const char *service,
const char *user_realm,
const char *user)
so likeβ¦ what does she do? sasl_user_exists will check if a user exists on the server. that's it, that's the whole job, and she ate. π₯
π Parameters π
the way that every single one of these matters, let's go:
connβ the SASL context for this connection (your main character, lowkey)serviceβ Service name, orNULL(and if you passNULL, it uses the service name of the connection context π)user_realmβ Realm to check in, orNULL(andNULLhere means the default realm, periodt)userβ User name to check for existence. literally just the name, bestie. π
π RETURN VALUE π
SASL functions should return SASL return codes β that's the whole system, no exceptions. peek at sasl.h for a complete list if you wanna see all of them, because there are many. and for the record: SASL_OK indicates success. so if you see SASL_OK, you're slaying. if you don'tβ¦ π vibe check failed, go read the error codes.
π§ SEE ALSO π§
go read these next, iykyk:
RFC 4422:saslman:sasl(3):saslman:sasl_errors(3)
π AUTHOR π
The Cyrus Team. icons only. π
πΈ COPYRIGHT πΈ
1993-2016, The Cyrus Team. yeah, that's a long legacy, we love a long-running queen.
this page is from version2.1.28, datedFebruary 18, 2022β and that's the wholeSASL_USER_EXISTS(3)story, bestie. go check those users, but stay safe out there π«Άβ¨π
π¦ 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