Build Service needs an openid.

Imagine following case: upstream needs an environment to reproduce build failure/ test failure, the best option would be osc co prj/pkg; osc build; osc chroot. But that requires Novell account. Having openid here will lower down the barrier.

Webui now works with Persona. API uses Devise with ichain plugin.

TODO:
*Generate token from WebUI, so we can talk to API directly *Don't generate passwords for Persona logins *Try Coolo's patches

Looking for hackers with the skills:

obs openid

This project is part of:

Hack Week 10

Activity

  • over 10 years ago: ancorgs disliked this project.
  • over 11 years ago: matejcik liked this project.
  • over 11 years ago: xnull joined this project.
  • over 11 years ago: k0da liked this project.
  • over 11 years ago: k0da started this project.
  • over 11 years ago: tampakrap liked this project.
  • over 11 years ago: ancorgs liked this project.
  • over 11 years ago: jospoortvliet liked this project.
  • over 11 years ago: bmwiedemann liked this project.
  • over 11 years ago: hennevogel liked this project.
  • over 11 years ago: k0da added keyword "obs" to this project.
  • over 11 years ago: k0da added keyword "openid" to this project.
  • over 11 years ago: k0da originated this project.

  • Comments

    • ancorgs
      over 11 years ago by ancorgs | Reply

      I would suggest to adapt OBS to use Devise [1], so you can use [2] for replacing current iChain (Novell account) login, [3] for implementing openid and A LOT of other authentication backends [4].

      [1] https://github.com/plataformatec/devise/ [2] https://github.com/openSUSE/deviseichainauthenticatable [3] https://github.com/nbudin/deviseopenidauthenticatable [4] https://github.com/search?q=devise

    • coolo
      over 11 years ago by coolo | Reply

      if your target is osc co; osc build for upstreams it would be much better to get rid of this strange limitation that you can only use the webui anonymously. Adrian is afraid that we will be overrun if we allow anonymous build, but seriously - you can do that now with an interconnect and there is no need to authentificate whatsoever.

    Similar Projects

    Switch software-o-o to parse repomd data by hennevogel

    Currently software.opensuse.org search is using the OBS binary search for everything, even for packages inside the openSUSE distributions. Let's switch this to use repomd data from download.opensuse.org


    Research openqa-trigger-from-obs and openqa-trigger-from-ibs-plugin by qwang

    Description

    openqa-trigger-from-obs project is a framework that OSD is using it to automatically sync the defined images and repositories from OBS/IBS to its assets for testing. This framework very likely will be used for the synchronize to each location's openqa include openqa.qa2.suse.asia Beijing local procy scc scc-proxy.suse.asia(although it's not a MUST to our testing) it's now rewriting requests to openqa.qa2.suse.asia instead of openqa.suse.de, the assets/repo should be consistent the format Beijing local openQA is maintaining an own script but still need many manually activities when new build comes, and not consistent to OSD, that will request many test code change due to CC network change

    Goals

    Research this framework in case it will be re-used for Beijing local openQA, and will need to be setup and maintained by ourselves

    Resources

    https://github.com/os-autoinst/openqa-trigger-from-obs/tree/master https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin

    beijing :rainbow machine


    Git CI to automate the creation of product definition by gyribeiro

    Description

    Automate the creation of product definition

    Goals

    Create a Git CI that will:

    • automatically be triggered once a change (commit) in package list is done.
    • run tool responsible to update product definition based on the changes in package list
    • test the updated product definition in OBS
    • submit a pull request updating the product definition in the repository

    NOTE: this Git CI may also be triggered manually

    Resources

    • https://docs.gitlab.com/ee/ci/
    • https://openbuildservice.org/2021/05/31/scm-integration/
    • https://github.com/openSUSE/openSUSE-release-tools


    Explore the integration between OBS and GitHub by pdostal

    Project Description

    The goals:

    1) When GitHub pull request is created or modified the OBS project will be forked and the build results reported back to GitHub. 2) When new version of the GitHub project will be published the OBS will redownload the source and rebuild the project.

    Goal for this Hackweek

    Do as much as possible, blog about it and maybe use it another existing project.

    Resources


    obs-service-vendor_node_modules by cdimonaco

    Description

    When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

    obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

    The tar will be used as source in the package building definitions.

    Goals

    • Create an obs service package that vendors the npm dependencies as tar archive.
    • Maybe add some macros to unpack the vendor package in the specfiles

    Resources


    OIDC Loginproxy by toe

    Description

    Reverse proxies can be a useful option to separate authentication logic from application logic. SUSE and openSUSE use "loginproxies" as an authentication layer in front of several services.

    Currently, loginproxies exist which support LDAP authentication or SAML authentication.

    Goals

    The goal of this Hack Week project is, to create another loginproxy which supports OpenID Connect authentication which can then act as a drop-in replacement for the existing LDAP or SAML loginproxies.

    Testing is intended to focus on the integration with OIDC IDPs from Okta, KanIDM and Authentik.

    Resources