Table of Contents
Hacker-ID
Identity provider for all things Hackeriet
Hacker-ID is a member-initiated service to provide a simple-to-use and universal base for implementing SSO services at Hackeriet.
This is a proof-of-concept to see how one could reasonably deploy IDP in a simple yet flexible way with few moving parts. I'm mainly testing this out as account management for a handful of projects I've planned for the space. Do not expect it to be widely used as of this moment.
Ask if you have any questions, need help, need an account, or want to integrate something.
Regards, 404'd
A simple self-service portal on https://idp.hackeriet.no provides basic account management features, together with a list of any Hacker-ID web applications you have access to.
Access control is currently managed through the Kanidm CLI. See the official docs for further details. Administrative UI for groups etc. will be added at a later date, either through Kanidm upgrades or using a separate companion service.
ACL structure
During the draft phase, the following groups have been configured:
| Name | Entry manager | Description |
|---|---|---|
hackeriet-members | hackeriet-styret | All currently active members |
hackeriet-styret | hackeriet-styret | Current board members |
hackeriet-alumni | hackeriet-styret | Members who are no longer active |
nettlaug-tenants | nettlaug-operators | People renting space/resources within nettlauget's infrastructure |
nettlaug-operators | nettlaug-operators | Core networking group, for infrastructure, switches, routing etc. |
service-idp-sysops | d404d@idp.hackeriet.no | Administrative privileges to Hacker-ID (Kanidm, SSH, and sudo) |
IDP admins may always step in to assist, shall any of the groups be orphaned (no active/reachable members).
Good to know
- Some information is publicly accessible, as required by unix/posix integrations: https://kanidm.github.io/kanidm/stable/accounts/anonymous_account.html#access
- Anonymous access will be removed once this draft is finalized: https://kanidm.github.io/kanidm/master/developers/designs/domain_join_machine_accounts.html
- Users are allowed to change all details about their profile! NEVER consider anything but the user UUID to be user identifiable (see the
subclaim oruuidclaims re. OpenIDC)- THIS INCLUDES THE USERNAME AND EMAIL
System setup
Rough notes for the moment:
- Hosted on idp1.hackeriet.no (DNS record pending, 10.10.50.52)
- Authentication realm is
idp.hackeriet.no - Public portal and API on https://idp.hackeriet.no
- Internal services (SSH, LDAP, RADIUS etc.) will be exposed on
int-idp.hackeriet.no- We won't be able to get LDAP certs for the right hostname on the internal interface… If this turns out to be a dealbreaker it might be better to solve this using NAT rather than moving the host entirely onto VLAN 130.
- Located in
/srv/kanidm- One docker compose stack with Traefik (for certificate issuance as LE needs this in-line) and Kanidm
- Communication between the two are encrypted using a self-signed certificate (Kanidm requires last-hop encryption)
- Created user and group “kanidm” in the host, which will represent the kanidm container's resources. Rights configured according to https://kanidm.github.io/kanidm/stable/security_hardening.html#security-hardening
- Kanidm includes built-in backup solution and replication
- No mirroring of the backups has been configured yet
- Set up kanidm-unixd for idp1.hackeriet.no
- Installed daemon
- Added to SSH config
- Added to nsswitch
- For Debian flavours incl. Ubuntu and Raspbian, installing
kanidm-unixdand configuring the two config files in/etc/kanidmshould be enough wrt. PAM - AppArmor default profiles blocks access to the service socket used, need to amend the profile with the correct paths then reload & restart