LCMAPS_VOMS_LOCALGROUP.MOD(8)
π LCMAPS_VOMS_LOCALGROUP.MOD π
okay so bestie, gather round, because this is lcmaps_voms_localgroup.mod(8) from section 8 of the manual, and she is that girl π
β¨ NAME β¨
lcmaps_voms_localgroup.mod β an LCMAPS plugin that switches up the user identity based on VOMS credentials, but likeβ¦ by local groups π«Ά
β¨ SYNOPSIS β¨
lcmaps_voms_localgroup.mod [-groupmapfile group-mapfile] [--map-to-
secondary-groups] [-mapall] [-mapmin number of minimal mappings]
β¨ DESCRIPTION β¨
So the VOMS localgroup acquisition plugin is a VOMS-aware plugin, and she's basically the sibling of the lcmaps_voms_localaccount.mod.8 plugin β same energy, except she's about groups instead of accounts. Not me having a whole fandom πΈ
What she does: she tries to find local groups (more specifically GroupIDs) based on the VOMS info that LCMAPS has on hand, especially the Fully Qualified Attribute Names (FQANs). She hunts for FQAN β localgroup mappings using the so-called group-mapfile (which is basically a grid-mapfile's cousin, iykyk).
Then the resulting list of groups gets looked up in /etc/groups and/or LDAP directories to figure out which Group IDs should be added as a mapping result. slay π₯
β¨ OPTIONS β¨
-groupmapfilegroup-mapfile β this file has to contain FQAN β local group name mappings, just like the grid-mapfile. The exact same formatting rules of the grid-mapfile apply to the group-mapfile, no cap. It is strongly advised to set it to an absolute path so you don't accidentally use the wrong file(path) π In a(setuid-)rootapplication, relative paths are taken with respect to/etc/grid-security/. And it is important to not mix the grid-mapfile and group-mapfile β they are not the same girl, do not confuse them π--map-to-secondary-groupsβ when enabled, the plug-in will map also the first FQAN of the user to secondary Group IDs, which means there will be no primary Group ID set by this plug-in while it's enabled. Also note: even if the first FQAN does not give a mapping, there will still be no primary Group ID set by this plug-in. So like, primary Group ID? Not today β¨-mapallβ when enabled, a failure gets triggered if not all of the FQANs were successfully mapped to primary or secondary Group IDs. She's an all-or-nothing queen π-mapminminimum number of mappings β this option sets a minimum amount of FQANs that have to be mapped for the plugin to succeed. Default is'0'. Note: if the minimum is unset or set to0, the plugin will succeed (if no other errors occur) even if no pool-groups were found. Lowkey generous of her π
β¨ RETURN VALUES β¨
LCMAPS_MOD_SUCCESSβ success. ate, no crumbs πLCMAPS_MOD_FAILβ failure. it's giving sad girl hours π
β¨ BUGS β¨
Please report any errors to the Nikhef Grid Middleware Security Team <grid-mw-security-support@nikhef.nl>. They wanna hear it fr fr π
β¨ SEE ALSO β¨
lcmaps.db(5), lcmaps(3).
β¨ AUTHORS β¨
LCMAPS and the LCMAPS plug-ins were written by the Grid Middleware Security Team <grid-mw-security@nikhef.nl>. iconic behavior honestly π
Stichting FOM/Nikhef, February 6, 2015 β that's the whole vibe, that's the whole source and date, and this manual page? She said what she said. mwah π π¦
π¦ where this page comes from
- debian bookworm: lcmaps-plugins-voms 1.7.1-1+b2 Β· Apache-2.0
- debian trixie: lcmaps-plugins-voms 1.7.1-2 Β· Apache-2.0
- ubuntu jammy: lcmaps-plugins-voms 1.7.1-1 Β· Apache-2.0
- ubuntu noble: lcmaps-plugins-voms 1.7.1-1ubuntu2 Β· Apache-2.0
- ubuntu questing: lcmaps-plugins-voms 1.7.1-2
- ubuntu resolute: lcmaps-plugins-voms 1.7.1-2build1 Β· Apache-2.0
- ubuntu stonking: lcmaps-plugins-voms 1.7.1-3 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms