Bug 1336236
| Summary: | hammer can't create external groups based on IPA/IdM integration | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Paul Armstrong <parmstro> |
| Component: | Users & Roles | Assignee: | Dominik Hlavac Duran <dhlavacd> |
| Status: | CLOSED ERRATA | QA Contact: | Sanket Jagtap <sjagtap> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1.8 | CC: | bkearney, ehelms, fgarciad, pa.van.der.sar, sjagtap, wpinheir |
| Target Milestone: | 6.4.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-16 18:53:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Paul Armstrong
2016-05-15 23:37:18 UTC
Created redmine issue http://projects.theforeman.org/issues/15286 from this bug Upstream bug component is Provisioning Upstream bug component is Users & Roles Upstream bug assigned to jmagen Upstream bug assigned to dhlavacd Upstream bug assigned to dhlavacd Did this magically appear somewhere along the road??
[root@sat6 parmstro]# hammer user-group external --help
Usage:
hammer user-group external [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND subcommand
[ARG] ... subcommand arguments
Subcommands:
create Create an external user group linked to a user group
delete Delete an external user group
info Show an external user group for user group
list List all external user groups for user group
refresh Refresh external user group
update Update external user group
Options:
-h, --help print help
Hi Paul, I believe this BZ is its way to be fulfilled, however it doesn't fully work in 6.2.12 as of today. When you issue something like : % hammer user-group external create --name IDM-Group --user-group Satellite-Group --auth-source-id 3 ... you still have no means to check what your auth-source-id should be. Currently API does not expose non-LDAP auth sources (and thus hammer). Hi All, I think that you were typing "on its way to being fulfilled" and had a typing skip. Thanks! Is there any way to prioritize this? We need this for automation when building environments that integrate IdM. I really would hate to have to run a sql query to get this - it is just wrong. (External id = 4 in my DB today) Cheers, Paul Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15286 has been resolved. Build: Satellite 6.4.0 snap9 -bash-4.2$ psql -d foreman -c "select id,name,type from auth_sources;" id | name | type ----+-------------+-------------------- 1 | Internal | AuthSourceInternal 2 | Hidden | AuthSourceHidden 3 | win2012R2AD | AuthSourceLdap 5 | External | AuthSourceExternal (4 rows) [root@sgi-uv20-01 ~]# hammer auth-source list ---|-------------|-------------------- ID | NAME | TYPE OF AUTH SOURCE ---|-------------|-------------------- 1 | Internal | AuthSourceInternal 3 | win2012R2AD | AuthSourceLdap 5 | External | AuthSourceExternal ---|-------------|-------------------- hammer> user-group create --name foobar User group [foobar] created. hammer> user-group external create --auth-source-id 5 --name foobargroup --user-group foobar External user group created. hammer> user-group external list --user-group foobar ---|-------------|------------ ID | NAME | AUTH SOURCE ---|-------------|------------ 1 | foobargroup | External ---|-------------|------------ *** Bug 1448179 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927 |