adsysctl update with a domain user fails if KRB5CCNAME is not set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
adsys (Ubuntu) |
Fix Released
|
Critical
|
Gabriel Nagy |
Bug Description
In an environment where /etc/krb5.conf sets "default_
If you either export the variable with the path to the kerberos ticket OR run the command "adsysctl update <user@domain> <path_to_
The adsysctl command should fallback to the default location when KRB5CCNAME is not defined or have a mechanism to query klist and find the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It seems like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https:/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSign
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041b
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2Availability
Ec2Imageid: ami-00094f7041b
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
Changed in adsys (Ubuntu): | |
importance: | Undecided → Critical |
status: | Confirmed → Triaged |
assignee: | nobody → Gabriel Nagy (gabuscus) |
Status changed to 'Confirmed' because the bug affects multiple users.