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
This project is part of:
Hack Week 10
Activity
Comments
-
about 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
-
about 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
Implement a full OBS api client in Rust by nbelouin
Description
I recently started to work on tooling for OBS using rust, to do so I started a Rust create to interact with OBS API, I only implemented a few routes/resources for what I needed. What about making it a full fledged OBS client library.
Goals
- Implement more routes/resources
- Implement a test suite against the actual OBS implementation
- Bonus: Create an osc like cli in Rust using the library
Resources
- https://github.com/suse-edge/obs-tools/tree/main/obs-client
- https://api.opensuse.org/apidocs/
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
New features in openqa-trigger-from-obs for openQA by jlausuch
Description
Implement new features in openqa-trigger-from-obs to make xml more flexible.
Goals
One of the features to be implemented: - Possibility to define "VERSION" and "ARCH" variables per flavor instead of global.
Resources
https://github.com/os-autoinst/openqa-trigger-from-obs
Learn about OSB and contribute to `kustomize` and `k9s` packages to add ARM arch by dpock
Description
There are already k9s
and kustomize
packages that exist for openSUSE today. These could be used as the source for these binaries in our rancher projects. By using them we would benefit from CVE fixes included in our distribution of the packages not in cluded upstream. However they are not providing arm package builds which are required.
Goals
- [ ] Update the kustomize package in OBS to use the newest version and send change request
Resources
- k9s: https://build.opensuse.org/package/show/openSUSE:Factory/k9s
- kustomize: https://build.opensuse.org/package/show/openSUSE:Factory/kustomize
- Learning Docs: https://confluence.suse.com/display/packaging/Training%2C+Talks+and+Videos
Learn obs/ibs sync tool by xlai
Description
Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.
Goals
Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.
Resources
- https://github.com/os-autoinst/openqa-trigger-from-obs
- https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads
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