The error shown in the attachment of this report is really a backend problem. Reassigning.

Pavol,

I think the update did succeed.  Can you do a refresh and confirm that?

thanks,
James

fixed in ansible_tower_client https://github.com/ansible/ansible_tower_client_ruby/pull/92

and release via 0.12.1 https://github.com/ansible/ansible_tower_client_ruby/commit/e33587b38644f6a1a6f2124ead2722c3e9df9637

so it should make it into the next build

Milan, can you have a look at Pavols screenshots? Looks like the ec2 credentials should be prefilled with ****, like the other.

Maybe the error in the attached log is unrelated (but fixed anyway)

The problem here is that the UI form we're looking at works with our
rest API. And that API does not return this piece of information
for the given credential resource. I'm not even sure if we store this
info in ManageIQ DB or whether it's contained just in Ansible.

Nevertheless, we're not rendering anything in the UI, since there's
basically nothing to render.

Milan,

The API_ATTRIBUTES give you some hint by :type => :password

:security_token => {
      :type       => :password,
      :label      => N_('STS Token'),
      :help_text  => N_('Security Token Service(STS) Token for this credential'),
      :max_length => 1024
    }

See if you can make use of that.

James

(In reply to James Wong from comment #11)
> Milan,
> 
> The API_ATTRIBUTES give you some hint by :type => :password
> 
> :security_token => {
>       :type       => :password,
>       :label      => N_('STS Token'),
>       :help_text  => N_('Security Token Service(STS) Token for this
> credential'),
>       :max_length => 1024
>     }
> 
> See if you can make use of that.

Yes. I am making use of that. Though this is unrelated to the problem
we're discussing.

Jillian,

Can you check with Alberto to see if API can unpack the options field from credential and send along to UI?

Thanks,
James

Milan,

So API does send you the 'options' attribute of the credential(authentication). It's a hash containing these extra attributes there.  Can you see UI can make use of that?

thanks,
James

Pavol, so this BZ is marked a POST with Marcel's fix. Do you mind create another bug tract this 'original' issue you are reporting?

(In reply to James Wong from comment #17)
> Milan,
> 
> So API does send you the 'options' attribute of the
> credential(authentication). It's a hash containing these extra attributes
> there.  Can you see UI can make use of that?

UI is making use of those options.

Now I see the problem:

The value of `usename` (described in API_ATTRIBUTES) is not stored in `options`, but in native attribute userid and UI has no info to link the two.