lsm_iscsi_chap_auth(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

πŸ’– lsm_iscsi_chap_auth β€” ok so we're doing iSCSI CHAP auth πŸ’–

Bestie. Sit down. Grab a strawberry πŸ“. We are in the Libstoragemgmt C API Manual and today's main character is lsm_iscsi_chap_auth, which sets up your iSCSI CHAP authentication β€” both directions, inbound and outbound. Yes, both. She's thorough. πŸ’…


✨ SYNOPSIS ✨

int lsm_iscsi_chap_auth (lsm_connect *conn, const char *init_id, const char *in_user, const char *in_password, const char *out_user, const char *out_password, lsm_flag flags);

Look at all those arguments. Six of them plus flags. It's giving thorough. 🌈


πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid connection pointer. Like, actually valid. A real one. If it's not valid we're gonna have a whole situation (see RETURN, bestie).
  • init_id β€” a String. This is the iSCSI Initiator IQN. That's your initiator's whole government name.
  • in_user β€” a String. The inbound user name. 🫢
  • in_password β€” a String. The inbound password. Keep it secret, keep it safe πŸ”’
  • out_user β€” a String. The outbound user name.
  • out_password β€” a String. The outbound password. Also secret. Obviously. πŸ™ˆ
  • flags β€” reserved for future use, so it must be LSM_CLIENT_FLAG_RSVD. Don't get creative with this one, it's not that kind of party. 🚫

🌸 VERSION 🌸

1.0 β€” she's been here a minute and she knows what she's doing. ⭐


πŸ¦‹ DESCRIPTION πŸ¦‹

Set the username password for iSCSI CHAP authentication, inbound and outbound.

That's it. That's the whole vibe. You hand her a connection, an initiator IQN, and the in/out credentials, and she makes the CHAP auth happen. Periodt. ✨


πŸ”₯ RETURN πŸ”₯

She gives you back an error code, enumerated by lsm_error_number. Here's the whole menu, no skips:

  • LSM_ERR_OK β€” on success. Slay! The good one. We love her. πŸ‘‘
  • LSM_ERR_INVALID_ARGUMENT β€” when it's not a valid lsm_connect pointer, or the flags are invalid. Yeah, she checks. She always checks. πŸ’€
  • LSM_ERR_NO_SUPPORT β€” not supported. It's not you, it's the backend. 😭

Heads up bestie: if your conn pointer is fake or your flags isn't LSM_CLIENT_FLAG_RSVD, you're getting LSM_ERR_INVALID_ARGUMENT back and honestly? You earned it. πŸ’…

That's the whole page, fr fr. Written up in the Libstoragemgmt C API Manual, version-dated February 2026, and yeah β€” the girl is literally named lsm_iscsi_chap_auth(3). Iykyk. πŸŽ€πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from