RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #961228 +++

Is this script supposed to be part of the openlmi-providers examples or distribution? Please feel free to close this bug if that's not the case.

http://jdennis.fedorapeople.org/realmd-cim

It's not included in the openlmi-providers repository.

Secondly, it makes you type two passwords on the command line. This is insecure.

--- Additional comment from John Dennis on 2013-05-09 08:24:24 EDT ---

This script was in the original git repo under doc/examples, the only reason for the link in comment #1 was to make easily available for test day.

The script is supposed to an example "scription". At the time of it's writing scripton's had not been nailed down including the common connect and authenticate part which is supposed to be shared between scriptions. So while the method to get the password may not be ideal it was a place holder until the scription framework was worked out.

As John had mentioned earlier: the script is an example of how to use the provider remotely.  In it's current state it can't be a part of the installation as an executable utility.