We have a java-based application to which we need to connect via a browser
As such we have configured transparent login to fill in the different fields by using mouseclicks and keystrokes, and this appears to work when using the Learning tool and the debug mode
However, when using the actual Transparent login in production, the password is never written, and sometimes not even the rest of the information, like IP, username or any arbitrary text
There may be several causes for this but, fundamentally, when using the mouseclick and keystroke mechanism we are in fact configuring a position in the screen where PAM should be writing the values specified. Since we are not putting a reference to a class, this is purely positional.
This means that if the final screen where we are writing the data to differs from the one we used when doing the initial Transparent Login configuration, the system may be trying to write to the wrong position in the browser. There are at least two situations when this may be occurring
Besides this we need to take into account that starting 2.8, the passwords are not being sent from the PAM server to the Transparent login backend, but instead they are being pulled by the transparent login backend from the PAM server. This means that any miscommunication, for instance, because of a DNS name resolution failure from the transparent login backend to the PAM server, or if a load balancer is configured without session persistence, may result in the transparent login machine not being efficiently communicating with the PAM server and it may not be retrieving the password for writing.
CA PAM 2.7.X and 2.8.X
Please try the following resolutions