Linking Tower's username and VMDB Authentication.userid for UI edit rendering #14900

jameswnl · 2017-04-26T16:25:56Z

This is part of https://bugzilla.redhat.com/show_bug.cgi?id=1444398. The bug thread is a bit distracted by other issue, hopefully this can help cut to the chase:

usename is described in API/EXTRA_ATTRIBUTES. However its value is not stored in the options hash, but in the native Authentication model attribute userid.

UI has no information to link the two and so when rendering an Edit page, UI can't populate the field with existing value.

So we need a mechanism to bridge them. (For this particular issue, the username is the Access Key in the screen shot.)

@mzazrivec @Fryguy @blomquisg
cc @jntullo

The text was updated successfully, but these errors were encountered:

jameswnl · 2017-04-26T16:30:53Z

I can think of the following ways solving this,

UI can hardcode this
Enhance the meta data and so UI can know where to look (and @mzazrivec just shot it down) e.g.

   :userid => {
      :label     => N_('Access Key'),
      :help_text => N_('AWS Access Key for this credential'),
      :required  => true
    }
to
   :userid => {
      :label        => N_('Access Key'),
      :help_text    => N_('AWS Access Key for this credential'),
      :required     => true,
      :native_attr  => true
    }

Credential implements a reader/writer for all the options attribute. (I know @bdunne prefer not to)
Pack :username/:userid into the options hash and don't re-use the userid attribute of Authentication. I.e. all the attributes being described by API_ATTRIBUTES would have their values stored in options. So consumers would consult API_ATTRIBUTES and retrieve all corresponding values from options (PR Pack Tower credential's username into the hash of authentication.options #14942) . (I know @Fryguy prefer not to)

So, someone has to come up with other ways

jameswnl · 2017-04-27T19:56:55Z

@durandom @bdunne any suggestion?

durandom · 2017-04-27T19:58:51Z

the BZ tracking this is actually https://bugzilla.redhat.com/show_bug.cgi?id=1446033

blomquisg · 2017-04-27T20:16:04Z

So, can we go with the first option?

UI can hardcode this

EDIT

Sorry, this isn't a real suggestion. But, I'm completely lost as to what the underlying problem actually is here.

durandom · 2017-04-27T20:29:57Z

I dont get this :( Are we returning the data via the rest api or not? From what I've read, we do, but at a different place. Reading #14902 (comment) seems we should make GET, POST and OPTIONS consistent.

@jntullo can you comment on @mzazrivec statement?

jntullo · 2017-04-27T20:37:17Z

The information is being returned via the API, but in a different place than is being specified when you make a call to OPTIONS to get information about the fields.

On the last option, instead of storing the :username into the options hash, would it be possible to just append it to that hash when it's being returned (this way we don't have to worry about the two fields being out of sync, but it is still being returned)? Running out of ideas otherwise...

blomquisg · 2017-04-27T20:38:25Z

@jntullo can you point to some code that shows where this is breaking down?

I'm completely lost in trying to understand the difference between username and userid in these various contexts.

durandom · 2017-04-27T20:40:07Z

The information is being returned via the API, but in a different place than is being specified when you make a call to OPTIONS to get information about the fields.

why cant it be in the same place?

could you show the API json examples?

jntullo · 2017-04-27T20:41:50Z

@blomquisg this is breaking down because the model is telling the user that this information should be stored in userid https://github.com/ManageIQ/manageiq/blob/master/app/models/manageiq/providers/ansible_tower/shared/automation_manager/amazon_credential.rb#L5-L8 but it is actually stored as username on the model itself

jntullo · 2017-04-27T20:43:09Z

@durandom I am not sure, that is less of an API question and more of a question for @jameswnl

durandom · 2017-04-27T20:47:01Z

@jntullo ok, I think I got username vs userid: this would work if settle on the correct field (which is userid)

But what about password and security_token. The UI cant display them. Are you returning them via the REST API?

durandom · 2017-04-27T21:00:58Z

durandom · 2017-04-27T21:31:32Z

So, ignore the view screenshots, they are not using the rest api

durandom · 2017-04-27T21:35:58Z

{  
   "href":"https://10.8.198.79/api/authentications/9",
   "id":9,
   "name":"awssadf",
   "userid":"asdasd",
   "resource_id":1,
   "resource_type":"ExtManagementSystem",
   "created_on":"2017-04-27T19:56:21Z",
   "updated_on":"2017-04-27T21:22:38Z",
   "type":"ManageIQ::Providers::EmbeddedAnsible::AutomationManager::AmazonCredential",
   "htpassd_users":[  

   ],
   "ldap_id":[  

   ],
   "ldap_email":[  

   ],
   "ldap_name":[  

   ],
   "ldap_preferred_user_name":[  

   ],
   "request_header_headers":[  

   ],
   "request_header_preferred_username_headers":[  

   ],
   "request_header_name_headers":[  

   ],
   "request_header_email_headers":[  

   ],
   "open_id_extra_scopes":[  

   ],
   "github_organizations":[  

   ],
   "manager_ref":"4",
   "options":{  
      "security_token":"$encrypted$"
   },
   "actions":[  
      {  
         "name":"delete",
         "method":"post",
         "href":"https://10.8.198.79/api/authentications/9"
      },
      {  
         "name":"edit",
         "method":"post",
         "href":"https://10.8.198.79/api/authentications/9"
      },
      {  
         "name":"delete",
         "method":"delete",
         "href":"https://10.8.198.79/api/authentications/9"
      }
   ]
}

durandom · 2017-04-27T21:36:55Z

{  
   "attributes":[  
      "authtype",
      "certificate_authority",
      "challenge",
      "created_on",
      "credentials_changed_on",
      "fingerprint",
      "github_organizations",
      "google_hosted_domain",
      "htpassd_users",
      "id",
      "last_invalid_on",
      "last_valid_on",
      "ldap_bind_dn",
      "ldap_email",
      "ldap_id",
      "ldap_insecure",
      "ldap_name",
      "ldap_preferred_user_name",
      "ldap_url",
      "login",
      "manager_ref",
      "name",
      "open_id_authorization_endpoint",
      "open_id_extra_authorize_parameters",
      "open_id_extra_scopes",
      "open_id_sub_claim",
      "open_id_token_endpoint",
      "open_id_user_info",
      "options",
      "public_key",
      "request_header_challenge_url",
      "request_header_email_headers",
      "request_header_headers",
      "request_header_login_url",
      "request_header_name_headers",
      "request_header_preferred_username_headers",
      "resource_id",
      "resource_type",
      "rhsm_pool_id",
      "rhsm_server",
      "rhsm_sku",
      "status",
      "status_details",
      "type",
      "updated_on",
      "userid"
   ],
   "virtual_attributes":[  
      "href_slug",
      "region_description",
      "region_number"
   ],
   "relationships":[  
      "authentication_configuration_script_bases",
      "authentication_orchestration_stacks",
      "configuration_script_bases",
      "configuration_script_sources",
      "orchestration_stacks",
      "resource"
   ],
   "subcollections":[  

   ],
   "data":{  
      "credential_types":{  
         "external_credential_types":{  
            "ManageIQ::Providers::AnsibleTower::AutomationManager::MachineCredential":{  
               "label":"Machine",
               "type":"machine",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential"
                  },
                  "password":{  
                     "type":"password",
                     "label":"Password",
                     "help_text":"Password for this credential"
                  },
                  "ssh_key_data":{  
                     "type":"password",
                     "multiline":true,
                     "label":"Private key",
                     "help_text":"RSA or DSA private key to be used instead of password"
                  },
                  "ssh_key_unlock":{  
                     "type":"password",
                     "label":"Private key passphrase",
                     "help_text":"Passphrase to unlock SSH private key if encrypted",
                     "max_length":1024
                  },
                  "become_method":{  
                     "type":"choice",
                     "label":"Privilege Escalation",
                     "help_text":"Privilege escalation method",
                     "choices":[  
                        "",
                        "sudo",
                        "su",
                        "pbrun",
                        "pfexec"
                     ]
                  },
                  "become_username":{  
                     "type":"string",
                     "label":"Privilege Escalation Username",
                     "help_text":"Privilege escalation username",
                     "max_length":1024
                  },
                  "become_password":{  
                     "type":"password",
                     "label":"Privilege Escalation Password",
                     "help_text":"Password for privilege escalation method",
                     "max_length":1024
                  },
                  "vault_password":{  
                     "type":"password",
                     "label":"Vault password",
                     "help_text":"Vault password",
                     "max_length":1024
                  }
               }
            },
            "ManageIQ::Providers::AnsibleTower::AutomationManager::ScmCredential":{  
               "label":"Scm",
               "type":"scm",
               "attributes":{  
                  "userid":{  
                     "label":"Access Key",
                     "help_text":"AWS Access Key for this credential"
                  },
                  "password":{  
                     "type":"password",
                     "label":"Secret Key",
                     "help_text":"AWS Secret Key for this credential"
                  },
                  "ssh_key_unlock":{  
                     "type":"password",
                     "label":"Private key passphrase",
                     "help_text":"Passphrase to unlock SSH private key if encrypted",
                     "max_length":1024
                  },
                  "ssh_key_data":{  
                     "type":"password",
                     "label":"Private key",
                     "help_text":"RSA or DSA private key to be used instead of password"
                  }
               }
            },
            "ManageIQ::Providers::AnsibleTower::AutomationManager::AmazonCredential":{  
               "type":"cloud",
               "label":"Amazon",
               "attributes":{  
                  "userid":{  
                     "label":"Access Key",
                     "help_text":"AWS Access Key for this credential",
                     "required":true
                  },
                  "password":{  
                     "type":"password",
                     "label":"Secret Key",
                     "help_text":"AWS Secret Key for this credential",
                     "required":true
                  },
                  "security_token":{  
                     "type":"password",
                     "label":"STS Token",
                     "help_text":"Security Token Service(STS) Token for this credential",
                     "max_length":1024
                  }
               }
            },
            "ManageIQ::Providers::AnsibleTower::AutomationManager::VmwareCredential":{  
               "label":"VMware",
               "type":"cloud",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential",
                     "required":true
                  },
                  "password":{  
                     "type":"password",
                     "label":"Password",
                     "help_text":"Password for this credential",
                     "required":true
                  },
                  "host":{  
                     "type":"string",
                     "label":"vCenter Host",
                     "help_text":"The hostname or IP address of the vCenter Host",
                     "max_length":1024,
                     "required":true
                  }
               }
            }
         },
         "embedded_ansible_credential_types":{  
            "ManageIQ::Providers::EmbeddedAnsible::AutomationManager::MachineCredential":{  
               "label":"Machine",
               "type":"machine",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential"
                  },
                  "password":{  
                     "type":"password",
                     "label":"Password",
                     "help_text":"Password for this credential"
                  },
                  "ssh_key_data":{  
                     "type":"password",
                     "multiline":true,
                     "label":"Private key",
                     "help_text":"RSA or DSA private key to be used instead of password"
                  },
                  "ssh_key_unlock":{  
                     "type":"password",
                     "label":"Private key passphrase",
                     "help_text":"Passphrase to unlock SSH private key if encrypted",
                     "max_length":1024
                  },
                  "become_method":{  
                     "type":"choice",
                     "label":"Privilege Escalation",
                     "help_text":"Privilege escalation method",
                     "choices":[  
                        "",
                        "sudo",
                        "su",
                        "pbrun",
                        "pfexec"
                     ]
                  },
                  "become_username":{  
                     "type":"string",
                     "label":"Privilege Escalation Username",
                     "help_text":"Privilege escalation username",
                     "max_length":1024
                  },
                  "become_password":{  
                     "type":"password",
                     "label":"Privilege Escalation Password",
                     "help_text":"Password for privilege escalation method",
                     "max_length":1024
                  },
                  "vault_password":{  
                     "type":"password",
                     "label":"Vault password",
                     "help_text":"Vault password",
                     "max_length":1024
                  }
               }
            },
            "ManageIQ::Providers::EmbeddedAnsible::AutomationManager::ScmCredential":{  
               "label":"Scm",
               "type":"scm",
               "attributes":{  
                  "userid":{  
                     "label":"Access Key",
                     "help_text":"AWS Access Key for this credential"
                  },
                  "password":{  
                     "type":"password",
                     "label":"Secret Key",
                     "help_text":"AWS Secret Key for this credential"
                  },
                  "ssh_key_unlock":{  
                     "type":"password",
                     "label":"Private key passphrase",
                     "help_text":"Passphrase to unlock SSH private key if encrypted",
                     "max_length":1024
                  },
                  "ssh_key_data":{  
                     "type":"password",
                     "label":"Private key",
                     "help_text":"RSA or DSA private key to be used instead of password"
                  }
               }
            },
            "ManageIQ::Providers::EmbeddedAnsible::AutomationManager::AmazonCredential":{  
               "type":"cloud",
               "label":"Amazon",
               "attributes":{  
                  "userid":{  
                     "label":"Access Key",
                     "help_text":"AWS Access Key for this credential",
                     "required":true
                  },
                  "password":{  
                     "type":"password",
                     "label":"Secret Key",
                     "help_text":"AWS Secret Key for this credential",
                     "required":true
                  },
                  "security_token":{  
                     "type":"password",
                     "label":"STS Token",
                     "help_text":"Security Token Service(STS) Token for this credential",
                     "max_length":1024
                  }
               }
            },
            "ManageIQ::Providers::EmbeddedAnsible::AutomationManager::VmwareCredential":{  
               "label":"VMware",
               "type":"cloud",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential",
                     "required":true
                  },
                  "password":{  
                     "type":"password",
                     "label":"Password",
                     "help_text":"Password for this credential",
                     "required":true
                  },
                  "host":{  
                     "type":"string",
                     "label":"vCenter Host",
                     "help_text":"The hostname or IP address of the vCenter Host",
                     "max_length":1024,
                     "required":true
                  }
               }
            }
         }
      }
   }
}

Fryguy · 2017-05-01T19:37:01Z

I'm not sure why the field can't just be called userid from the OPTIONS. Then we know that's a column and just write it into the column. I guess I don't understand why username needs to even be a thing. Same goes for password or any other column.

Fryguy · 2017-05-01T19:52:15Z

@mzazrivec @AparnaKarve I believe the issue here is the UI can't be sure from which field in the API request to get the value. Since userid, and password and perhaps others, are straight attributes, they will appear in the base during an API call. However, the rest appear under "options" heading in the API call.

Chopping down what @durandom wrote...

Here is an OPTIONS call where userid and another field appear the same...

   "data":{  
      "credential_types":{  
         "external_credential_types":{  
            "ManageIQ::Providers::AnsibleTower::AutomationManager::MachineCredential":{  
               "label":"Machine",
               "type":"machine",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential"
                  },
...
                  "become_username":{  
                     "type":"string",
                     "label":"Privilege Escalation Username",
                     "help_text":"Privilege escalation username",
                     "max_length":1024
                  },
...

However, when reading from the API, they appear like the following, so they are at different nestings, and thus the UI has no idea where to look.

{  
   "href":"https://10.8.198.79/api/authentications/9",
   "id":9,
   "name":"awssadf",
   "userid":"asdasd",
...
   "options":{  
      "become_username":"sdfjksdfj"
   },
...
}

Thus I recommend number 2, but would like to know why the idea was shot down. We can of course debate the name "native_attr", or whether we conversely mark only the ones that live under options. I am trying to come at this from an API perspective and not a pure UI perspective, so I am also trying to understand how regular API users might be confused by this. As such, @abellotti, how would this work from the manageiq-api-client standpoint?

Fryguy · 2017-05-01T19:56:43Z

Alternately, perhaps we should change the OPTIONS call to mirror the GET call by having a nested "options" key somewhere. That is, something like

   "data":{  
      "credential_types":{  
         "external_credential_types":{  
            "ManageIQ::Providers::AnsibleTower::AutomationManager::MachineCredential":{  
               "label":"Machine",
               "type":"machine",
               "attributes":{  
                  "userid":{  
                     "label":"Username",
                     "help_text":"Username for this credential"
                  },
...
                  "options": {
                     "become_username":{  
                        "type":"string",
                        "label":"Privilege Escalation Username",
                        "help_text":"Privilege escalation username",
                        "max_length":1024
                     },
...
                  },
...

@bdunne @jntullo @abellotti Thoughts?

jntullo · 2017-05-01T20:28:32Z

@Fryguy I believe the reasoning behind not choosing #2 is because then the way you create an authentication is different from the way you get an authentication and all of its attributes. I agree that it's probably not the best way to go because of that, as it's not intuitive from a user's perspective.

In other API collections such as ServiceTemplates, we ensure that the data is returned the same way that it was passed in.

with that said, I like your idea of having OPTIONS call mirror the GET call 😄

abellotti · 2017-05-01T20:32:13Z

👍 on the OPTIONS reflecting what GET call returns, would work with options, or any other nested/hash attributes.

AparnaKarve · 2017-05-01T21:20:28Z

@Fryguy Yes, the OPTIONS call mirroring the GET would be great!
That way we won't have any exception cases like userid

That said, I will wait for the new OPTIONS PR and hold off from making any changes in the UI (with regard to userid)

BTW, how do we plan to send password? Instead of sending a blank value can we send a value like $encrypted$ (the way security_token is currently sent) ?

Fryguy · 2017-05-01T21:25:51Z

password will never come back from the database, and I would even never send an encrypted string back to the caller. Just assume you won't have a value. I would also never send back security_token...that seems like a potential security issue IMO.

AparnaKarve · 2017-05-01T22:04:49Z

Ok, so for the password fields, the new and improved OPTIONS call should only send the attribute names like password and security_token and no values/encrypted strings etc

The only time the UI would be really dealing with a password would be when --
(a) creating a new Credential record
(b) updating the password for an existing Credential

durandom · 2017-05-02T10:15:32Z

password will never come back from the database, and I would even never send an encrypted string back to the caller. Just assume you won't have a value.

So here is how ansible tower handles this:

send $encrypted$ -> don't touch pw
send empty string -> clear pw
send string -> set pw

This way you can at least show **** for a set pw and '' for nothing

@jntullo do we do something similar in our API to retain a pw? Or do we implement PATCH requests to do partial updates?

jntullo · 2017-05-02T13:00:53Z

@durandom The API does partial updates. A lot of the specifics depend on the model itself - there's not much logic in the actual controller

jameswnl · 2017-05-02T14:08:18Z

In this case, model/backend doesn't really look into what is being passed to Tower (except translating userid to username. So PATCH without password field in the param hash would be fine.

AparnaKarve · 2017-05-02T15:36:53Z

@jameswnl What about the PUT call?
Currently the UI uses PUT for updates.
Will PUT work if the UI does not send password fields?

jameswnl · 2017-05-02T16:35:12Z

@AparnaKarve my understanding is: TowerClient Gem is always using patch https://github.com/jameswnl/ansible_tower_client_ruby/blob/c9e742fedde3308f4391bd315cd02029bd425371/lib/ansible_tower_client/base_model.rb#L83-L83

Fryguy · 2017-05-02T18:18:58Z

@durandom Oh you mean it sends LITERALLY $encrypted$ or are you saying it sends the encrypted garbage back to the user?

AparnaKarve · 2017-05-02T19:04:42Z

Yes, it's literally "$encrypted$"

In any case, the UI should not be sending any password fields if it's not creating a record or not updating a password field.
I'm going to change the PUT call that is currently being used for updating a record to PATCH, which would make the partial update work per above discussion #14900 (comment)

AparnaKarve · 2017-05-03T15:15:49Z

FYI, PATCH /api/authentications/<id> fails with this error:

no implicit conversion of String into Integer

abellotti · 2017-05-03T15:37:11Z

are you using the patch directives as mentioned in http://manageiq.org/docs/reference/latest/api/overview/http#updating-resources in the payload, or just the attributes ? in the latter case you probably just want a PUT or POST with "edit" action.

AparnaKarve · 2017-05-03T15:49:28Z

I was using just the attributes, so that could be the reason.

@abellotti @jntullo Any idea if PUT supports a partial update?
Per the above discussion, the UI would not be sending passwords in certain scenarios.

EDIT: Just to be very clear, I'm OK using PUT/PATCH as long as either call supports a partial update.

abellotti · 2017-05-03T17:10:04Z

PUT supports partial, essentially similar to a POST edit.

AparnaKarve · 2017-05-03T19:17:09Z

@durandom FYI: While the Notification in the UI displays the password as ******, the evm.log completely gives it away.
(Checkout :security_token=>"mypassword" in the log below -

evm.log:[----] I, [2017-05-03T12:04:06.474890 #20011:3fcd4b50a098]  INFO -- : MIQ(MiqQueue.put) Message id: [61576],  id: [], Zone: [default], Role: [ems_operations], Server: [], Ident: [generic], Target id: [], Instance id: [7], Task id: [], Command: [ManageIQ::Providers::EmbeddedAnsible::AutomationManager::AmazonCredential.update_in_provider], Timeout: [600], Priority: [20], State: [ready], Deliver On: [], Data: [], Args: [{:id=>7, :name=>"MyAmz288", :type=>"ManageIQ::Providers::EmbeddedAnsible::AutomationManager::AmazonCredential", :userid=>"admin288", :security_token=>"mypassword", :task_id=>80}]

durandom · 2017-05-03T20:06:15Z

@AparnaKarve nice find. Could you try to add security_token to PASSWORD_FIELDS and see if its filtered out then?

AparnaKarve · 2017-05-12T23:02:11Z

@jameswnl Would this PR #15084 address what @durandom suggested above?

jameswnl · 2017-05-15T13:32:01Z

@AparnaKarve yes, it would.

Fryguy · 2017-06-14T18:48:52Z

@jameswnl Is this issue still open?

jameswnl · 2017-06-14T18:59:43Z

no, closing it ....

ganeshgawali · 2020-03-23T18:45:23Z

Hello I am looking for to get the AWS credentials by calling Authentication API of manageIQ. Bur only able to see access key .. please help to get the secret key. Appreciate your help :)

Here is the sample data i am getting once i called /api/authentication

{
"href": "https://localhost:8443/api/authentications/10",
"id": "10",
"name": "ManageIQ::Providers::Amazon::CloudManager AWS-Ireland",
"authtype": "default",
"userid": "this must be the access key",
"resource_id": "14",
"resource_type": "ExtManagementSystem",
"created_on": "2020-03-18T11:41:54Z",
"updated_on": "2020-03-23T18:39:04Z",
"last_valid_on": "2020-03-23T18:39:04Z",
"last_invalid_on": null,
"credentials_changed_on": "2020-03-18T11:41:54Z",
"status": "Valid",
"status_details": "Ok",
"type": "AuthUseridPassword",
"fingerprint": null,
"challenge": null,
"login": null,
"public_key": null,
"htpassd_users": [],
"ldap_id": [],
"ldap_email": [],
"ldap_name": [],
"ldap_preferred_user_name": [],
"ldap_bind_dn": null,
"ldap_insecure": null,
"ldap_url": null,
"request_header_challenge_url": null,
"request_header_login_url": null,
"request_header_headers": [],
"request_header_preferred_username_headers": [],
"request_header_name_headers": [],
"request_header_email_headers": [],
"open_id_sub_claim": null,
"open_id_user_info": null,
"open_id_authorization_endpoint": null,
"open_id_token_endpoint": null,
"open_id_extra_scopes": [],
"open_id_extra_authorize_parameters": null,
"certificate_authority": null,
"google_hosted_domain": null,
"github_organizations": [],
"rhsm_sku": null,
"rhsm_pool_id": null,
"rhsm_server": null,
"manager_ref": null,
"options": null,
"evm_owner_id": null,
"miq_group_id": "2",
"tenant_id": "1",
"become_username": null,
"actions": [
{
"name": "delete",
"method": "post",
"href": "https://localhost:8443/api/authentications/10"
},
{
"name": "edit",
"method": "post",
"href": "https://localhost:8443/api/authentications/10"
},
{
"name": "edit",
"method": "patch",
"href": "https://localhost:8443/api/authentications/10"
},
{
"name": "edit",
"method": "put",
"href": "https://localhost:8443/api/authentications/10"
},
{
"name": "refresh",
"method": "post",
"href": "https://localhost:8443/api/authentications/10"
},
{
"name": "delete",
"method": "delete",
"href": "https://localhost:8443/api/authentications/10"
}
]
}

I am unable to get the secret key even though i saw the above closed thread.

jameswnl mentioned this issue Apr 26, 2017

Add native_attr to OPTIONS of Tower Credentials #14902

Closed

AparnaKarve mentioned this issue Apr 27, 2017

Create credentialModel elements once required data is available ManageIQ/manageiq-ui-classic#1091

Closed

jameswnl mentioned this issue Apr 28, 2017

Pack Tower credential's username into the hash of authentication.options #14942

Closed

AparnaKarve mentioned this issue May 2, 2017

Better password management in Ansible Credential Form ManageIQ/manageiq-ui-classic#1227

Merged

gmcculloug assigned jameswnl Jun 8, 2017

jameswnl closed this as completed Jun 14, 2017

Linking Tower's username and VMDB Authentication.userid for UI edit rendering #14900

Linking Tower's username and VMDB Authentication.userid for UI edit rendering #14900

Comments

jameswnl commented Apr 26, 2017 • edited Loading

jameswnl commented Apr 26, 2017 • edited Loading

jameswnl commented Apr 27, 2017

durandom commented Apr 27, 2017

blomquisg commented Apr 27, 2017 • edited Loading

durandom commented Apr 27, 2017

jntullo commented Apr 27, 2017 • edited Loading

blomquisg commented Apr 27, 2017

durandom commented Apr 27, 2017

jntullo commented Apr 27, 2017

jntullo commented Apr 27, 2017

durandom commented Apr 27, 2017

durandom commented Apr 27, 2017 • edited Loading

durandom commented Apr 27, 2017

durandom commented Apr 27, 2017

durandom commented Apr 27, 2017

Fryguy commented May 1, 2017

Fryguy commented May 1, 2017 • edited Loading

Fryguy commented May 1, 2017 • edited Loading

jntullo commented May 1, 2017 • edited Loading

abellotti commented May 1, 2017 • edited Loading

AparnaKarve commented May 1, 2017

Fryguy commented May 1, 2017

AparnaKarve commented May 1, 2017 • edited Loading

durandom commented May 2, 2017

jntullo commented May 2, 2017

jameswnl commented May 2, 2017

AparnaKarve commented May 2, 2017

jameswnl commented May 2, 2017

Fryguy commented May 2, 2017

AparnaKarve commented May 2, 2017

AparnaKarve commented May 3, 2017 • edited Loading

abellotti commented May 3, 2017

AparnaKarve commented May 3, 2017 • edited Loading

abellotti commented May 3, 2017

AparnaKarve commented May 3, 2017

durandom commented May 3, 2017 • edited Loading

AparnaKarve commented May 12, 2017

jameswnl commented May 15, 2017

Fryguy commented Jun 14, 2017

jameswnl commented Jun 14, 2017

ganeshgawali commented Mar 23, 2020 • edited Loading

jameswnl commented Apr 26, 2017 •

edited

Loading

jameswnl commented Apr 26, 2017 •

edited

Loading

blomquisg commented Apr 27, 2017 •

edited

Loading

jntullo commented Apr 27, 2017 •

edited

Loading

durandom commented Apr 27, 2017 •

edited

Loading

Fryguy commented May 1, 2017 •

edited

Loading

Fryguy commented May 1, 2017 •

edited

Loading

jntullo commented May 1, 2017 •

edited

Loading

abellotti commented May 1, 2017 •

edited

Loading

AparnaKarve commented May 1, 2017 •

edited

Loading

AparnaKarve commented May 3, 2017 •

edited

Loading

AparnaKarve commented May 3, 2017 •

edited

Loading

durandom commented May 3, 2017 •

edited

Loading

ganeshgawali commented Mar 23, 2020 •

edited

Loading