[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980462: ITP: oidc-agent -- Commandline tool for obtaining OpenID Connect Access tokens on the commandline



Package: wnpp
Severity: wishlist
Owner: Marcus Hardt <marcus@hardt-it.de>
X-Debbugs-Cc: debian-devel@lists.debian.org, marcus@hardt-it.de

* Package name    : oidc-agent
  Version         : 4.0.2
  Upstream Author : Gabriel Zachmann <gabriel.zachmann@kit.edu>
* URL             : https://github.com/indigo-dc/oidc-agent
* License         : MIT
  Programming Lang: C++
  Description     : Commandline tool for obtaining OpenID Connect Access tokens on the commandline

oidc-agent consists of five programs:
   - oidc-agent that handles communication with the OIDC provider
   - oidc-gen that generates config files
   - oidc-add that loads (and unloads) configuration into the agent
   - oidc-token that can be used to get access token on the command line
   - oidc-keychain that re-uses oidc-agent across logins

 The package is useful for using distributed infrastructures that make use
 of OpenID Connect (such as the European Federated Cloud, the Worldwide
 LHC Computing Grid).


 The package depends on a set of other packages:
        fakeroot,
        devscripts,
        libcurl4-openssl-dev (>= 7.35.0),
        libsodium-dev (>= 1.0.14),
        help2man (>= 1.46.4),
        libseccomp-dev (>= 2.1.1),
        libmicrohttpd-dev (>= 0.9.33),
        check (>= 0.10.0),
        pkg-config (>= 0.29),
        libsecret-1-dev (>= 0.18.4),
        libcjson-dev (>= 1.7.14),

 Other packages that depend on oidc-agent are not (yet) shipped via
 debian. Those include the unicore commandline client, udocker, and the
 watts client.

 I am not aware of other packages providing OpenID Connect Access Tokens
 on the commandline.

 Maintenance plan is that I can do it during my office hours at work. The
 same currently holds for the upstream developer.

 I am not looking for co-maintainers.

 I have looked for a sponsor, Micha Lenk is helping us a lot.


Reply to: