Red Hat Bugzilla – Bug 1336236
hammer can't create external groups based on IPA/IdM integration
Last modified: 2018-03-20 08:07:42 EDT
Description of problem:
hammer user-group external create requires auth_source_id which is not available when configuring IPA/IdM integration with
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. katello-installer --foreman-ipa-authentication=true
3. hammer user-group create --name=dummy --role-ids=1,2,3,4
User group [dummy] created
4. hammer user-group external create --name=dummy --user-group=dummy
Could not create external user group:
Missing arguments for 'auth_source_id'
--- No value of auth_source_id works
External group [dummy] created
[root@sat6 /]# hammer auth-source ldap list
ID | NAME | LDAPS? | PORT | SERVER TYPE
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 firstname.lastname@example.org
Upstream bug assigned to email@example.com
Did this magically appear somewhere along the road??
[root@sat6 parmstro]# hammer user-group external --help
hammer user-group external [OPTIONS] SUBCOMMAND [ARG] ...
[ARG] ... subcommand arguments
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
-h, --help print help
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).
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)
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15286 has been resolved.