shishi_cfg_authorizationtype_set(3)

πŸ“¦
version 1.0.3 Β· 2 versions
  • 1.0.3 Β· debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.2 Β· ubuntu jammy
, in debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ shishi_cfg_authorizationtype_set(3) ✨

okay so bestie, we're in the shishi manual section, and today's main character is shishi_cfg_authorizationtype_set β€” an API function that literally just tells shishi who's allowed in and how we're checking. let's get into it πŸ’…


🌸 NAME 🌸

shishi_cfg_authorizationtype_set β€” API function. that's it, that's the name, she's an API function and she's booked and busy πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <shishi.h>

int shishi_cfg_authorizationtype_set(Shishi * handle, char * value);

like, include the header, call the function, slay. that's the whole vibe ✨


πŸ’– ARGUMENTS πŸ’–

  • Shishi * handle β€” the Shishi library handle, and you gotta make her with shishi_init(). no handle, no service, periodt.
  • char * value β€” a string listing the acceptable authorization types. basically your lil guest list, but as text 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so what she does is set the configuration option "authorization-types" from value. the way that works is so cute actually: the string contains authorization types, and those types can be integers or names, separated by comma or whitespace. mix and match, she doesn't care, she's flexible like that 🌈

as an example, "k5login basic" would first check Kerberos5 authentication based on preset principals, and then fall back to the basic test of identical principal names. so it's giving "try the fancy door first, then the regular door" energy πŸšͺ✨ β€” order matters, bestie, it's a fallback chain, not a random grab bag.


⭐ RETURN VALUE ⭐

  • Returns SHISHI_OK if successful πŸ’–
  • and SHISHI_INVALID_ARGUMENT otherwise 😭

that's the whole vibe check. two outcomes, no in-between, no cap.


πŸ› REPORTING BUGS πŸ›

found a bug? not me being the one to tell you, but like β€” report bugs to <bug-shishi@gnu.org>. 🫢

GNU Shishi home page: http://www.gnu.org/software/shishi/

General help using GNU software: http://www.gnu.org/gethelp/


Copyright Β© 2002-2022 Simon Josefsson.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.

yes bestie, you can copy it, just keep the receipts (the copyright notice AND this notice). iconic behaviour, honestly πŸ‘‘

πŸ”₯ SEE ALSO πŸ”₯

the full documentation for shishi is maintained as a Texinfo manual. if the info and shishi programs are properly installed at your site, the command

info shishi

should give you access to the complete manual. iykyk πŸ“–βœ¨


and that's the page, babes πŸŽ€ β€” this was shishi version 1.0.3, from the shishi source, and it's the shishi_cfg_authorizationtype_set(3) page. go forth and authorize responsibly πŸ’–πŸ¦‹πŸŒΈ