Release adsys 0.12.0

Bug #2020682 reported by Denison Barbosa
This bug affects 1 person
Affects Status Importance Assigned to Milestone
adsys (Ubuntu)
Fix Released

Bug Description

ADSys is part of the enterprise desktop offerings and customers are requesting the new version to be released for 22.04 LTS.


* ADSys depends on Go 1.20, so the golang-1.20 package must be backported to 22.04 as well.
* The new version has some features that are heavily requested by enterprise customers running the LTS.

[Test Plan]

 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (;
 2. Install admx and adml files on your AD controller (;
 3. Configure some Group Policies in the AD server (;
 4. Install ADSys, reboot the machine and login in as an AD user;
 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine;

[Where problems could occur]

* ADSys can prevent authentication of AD users if some policies can't be applied;
* For local users, no impact will occur;

description: updated
summary: - [SRU] Release new adsys version to Jammy
+ Release adsys 0.12.0
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package adsys - 0.12.0

adsys (0.12.0) mantic; urgency=medium

  [ Denison Barbosa ]
  [ Didier Roche ]
  [ Gabriel Nagy ]
  [ Jean-Baptiste Lallement ]
  * Release 0.12.0 (LP: #2020682)
    - Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    - Go implementation for the user mount handler
    - Remove Rust source code from adsys
    - Rework Kerberos ticket handling logic:
      - to satisfy the Heimdal implementation of Kerberos, we now store and use
        a root-owned copy of the cached ticket
      - the ticket lifetime is still handled via a symlink, and the copy is
        kept up to date based on the original ticket timestamp
    - Ensure empty state for dconf policy
    - Handle case mismatches in GPT.INI file name
    - Refactor ListActiveUsers gRPC function
    - Add adsysctl policy purge command to purge applied policies
    - Rework policy application sync strategy
    - Print logs when policies are up to date
    - Bump Go version to 1.20
    - Update dependencies to latest:
    - CI and quality of life changes not affecting package functionality:
      - peter-evans/create-pull-request
      - Apply clang-format to C source files
      - Remove Rust related code from CI and tests
      - Improve test consistency
      - Fix documentation example images

 -- Denison Barbosa <email address hidden> Fri, 26 May 2023 07:11:55 -0400

Changed in adsys (Ubuntu):
status: New → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Please see - please address the concerns written there before we proceed with this SRU.

Changed in adsys (Ubuntu Jammy):
status: New → Incomplete
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Also, since I don't know the adsys codebase, how does the automated testing story for it look like? Does it have a thorough test suite? Autopkgtests?

Revision history for this message
Denison Barbosa (justdenis) wrote :

Hey, @sil2100! ubuntu-proxy-manager is just a suggested package and its absence does not impact adsys functionality. We will address the dependency later but do not want to block the release of adsys on this package.

Our whole test suite is automated through GitHub actions, which can be found at: Every Go package developed by us is tested and we also have integration tests for the whole adsys package, with 86% source coverage, as shown on

Revision history for this message
Chris Halse Rogers (raof) wrote :

I see that we've done this sort of wholesale backport once before, but this doesn't seem like it falls under the "other safe cases" part of the SRU criteria:

It seems like this should have a more formal process? I don't see any special case documentation on the wiki, nor can I find it discussed on ubuntu-release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.