Search Criteria
Package Details: kanidm-server 1.5.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/kanidm.git (read-only, click to copy) |
---|---|
Package Base: | kanidm |
Description: | kanidm server for idendity management, supports RADIUS, ssh key management. |
Upstream URL: | https://github.com/kanidm/kanidm |
Keywords: | authentication iam identity identity-management idm ldap oidc radius rust scim security ssh-authentication webauthn |
Licenses: | MPL-2.0 |
Conflicts: | kanidm-server-git |
Provides: | kanidm-server |
Submitter: | soloturn |
Maintainer: | soloturn (cubi, fossdd, Doridian) |
Last Packager: | Doridian |
Votes: | 7 |
Popularity: | 1.10 |
First Submitted: | 2021-04-02 14:45 (UTC) |
Last Updated: | 2025-04-15 20:24 (UTC) |
Dependencies (3)
- libgit2 (libgit2-gitAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- systemd (systemd-chromiumosAUR, systemd-fmlAUR, systemd-selinuxAUR, systemd-gitAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 Next › Last »
Doridian commented on 2024-11-15 23:27 (UTC) (edited on 2024-11-16 00:55 (UTC) by Doridian)
Just installed this package and noticed an issue:
/usr/lib/systemd/system/kanidm-unixd.service
refers toshadow
inSupplementaryGroups
. Arch (at least on any of my systems) does not have a group calledshadow
, causing kanidm-unixd to fail to start (well, causing systemd to fail to start it, rather).Likely just a simple patch to remove the group from the service file? For now I did a
groupadd shadow
to bypass the startup failure, and everything else seems to be just fine.Doridian commented on 2024-11-15 20:37 (UTC) (edited on 2024-11-15 23:21 (UTC) by Doridian)
Hey, is any help needed maintaining this package? I'd love to help if that's the case.
I noticed recently 1.4.x released 2 weeks ago and the 1.3.3 version currently released also seems to no longer build for me on current Arch.
For now I have created my own copy of this repo on GitHub with a working 1.4.2 build: https://github.com/Doridian/kanidm-aur/commit/a6e17e49649360fd12eff2e1e2ab5072fbd0859e (they forgot to update their lockfile hence the .patch being needed for specifically 1.4.2 to make --locked work)//EDIT: Updated git hash as I realized I initially broke the server package build due to WebUI updates, fixed and tested that it works this time!
//EDIT2: Just noticed it was updated. Thanks :)
soloturn commented on 2024-07-19 22:25 (UTC) (edited on 2024-07-19 22:37 (UTC) by soloturn)
fossdd, added you as co maintainer, and updated to kanidm-1.2.3.
fossdd commented on 2024-06-06 10:15 (UTC)
hey, i'd like to co-maintain this package as I also maintain the Alpine Linux port of kanidm. I'd upgrade kanidm to 1.2.3 as this would ig. also fix the current build issue.
yaleman commented on 2024-05-06 22:02 (UTC)
Hey folks, this package is failing to build because you're building everything - (ref https://github.com/kanidm/kanidm/issues/2751) can I suggest you build the specific binaries instead of the dev things like Orca?
cubi commented on 2023-05-10 20:03 (UTC)
@DevPGSV thanks for sharing and the notification. I have updated the PKGBUILD.
DevPGSV commented on 2023-05-09 22:51 (UTC) (edited on 2023-05-09 22:52 (UTC) by DevPGSV)
I had the need to use:
As I needed to connect to a server with:
And there is a JWT incompatibility between alpha.11 (current package build) and alpha.12 (latest available version).
I ended up with a working version:
soloturn commented on 2021-10-09 04:34 (UTC) (edited on 2021-10-09 04:34 (UTC) by soloturn)
@cubi, thanks for asking thoughts concerning a metapackage. my reasoning centers around why "metapackage" as such do exist: https://lists.archlinux.org/pipermail/arch-dev-public/2019-January/029435.html. using such a concept for kanidm seems overkill. we only have server and client and a single dependency.
soloturn commented on 2021-10-08 16:32 (UTC) (edited on 2021-10-08 16:35 (UTC) by soloturn)
why i like to have 2 versions installed, @cubi? mainly to set the path and try without going through any complication of creating directories, checking out, separate builds etc. just set the path and try one or the other, for typical client apps very practical. python2, python3, java11, java17, swiftlang-5.4.2, swiftlang-5.5, and so on. for kanidm it would not rebuild, but just register the services for one or the other. but - i did not want to do it yet and thus not really missed the feature ... so lets not move and wait until sombody is missing it more :)
« First ‹ Previous 1 2 3 Next › Last »