Created attachment 1870002 [details]
I'd like to label the inputs like this

At the very least, I need some kind of hacky not-ideal work around to fix these labels in the current version until a proper fix can get worked on.

Many thanks!

I just noticed that in RHCS 9 we did this in a profile on a particular field input to set the input label:


input.i2.class_id=genericInputImpl                                                                                                                                                                                                             
input.i2.params.gi_display_name0=Client Name (no app- prefix)                                                                                                                                                                                  
....
input.i2.params.gi_param_enable0=true                                                                                                                                                                                                          
input.i2.params.gi_param_name0=sn_cert_name                                                                                                                                                                                                    


This demonstrates how we were able to label a *particular* field input label. When our users see this in the web browser they see a field labeled "Client Name (no app- prefix)"


I would like to know how to do this with the "LDAP Password" input field.

In my original comment I said

> [...] if, for example, in the CS.cfg I could have configurable [...]

Upon reflection, this would be best if the configuration settings could be made on a per-profile basis. For example, I noticed in some profiles that very specific details about the parameters can be set:

> caTokenUserSigningKeyEnrollment.cfg:policyset.set1.p1.default.params.ldap.ldapconn.secureConn=false

I don't know how flexible this system is, or if my idea applies at all here. Is it possible to set default field labels for the LDAP Username/Password fields in the CS.cfg and then override them on a case by case basis per-profile?

Here is my use case:

1. We have some profiles (most) they are for humans to use, the users enter their ID and 2-Factor Pin+Token
2. Some profiles are only for robots (service accounts) to use, the information entered is the robot UID and the static service account password

Having these fields clearly labeled between profiles would improve our users' experiences and lead to fewer questions and errors.

So in the case of #1 it would be ideal if we could use default labels from the CS.cfg

In the case of #2 we would like to override those profile labels in the profile, for example (just making this up as I go along here):

> auth.instance_id=UserDirAppEnrollment
> auth.instance.UserDirAppEnrollment.uidInputLabel=Service Account UID
> auth.instance.UserDirAppEnrollment.pwInputLabel=Service Account Password

----


If "inheriting CS.cfg defaults" and "overriding per-profile" is out of the question, I'd be satisfied with providing the uid/pwd input labels in each profile.

Thanks so much!

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.