Re: Junos Pulse Desktop, Username Password fields

Lilja_ · ‎06-03-2013

Is there a way to control the name of the input fields in Junos Pulse Desktop client (Win/OSX)?

The sign-in page settings only affect web-login.

It seems like depending on if it's a RADIUS server or a LDAP server that is used as auth.server, the Inputfield-name alters between "Passcode" (RADIUS) and "Password" (LDAP).

zanyterp_ · ‎06-03-2013

No, they cannot be controlled/modified for the client. What is the desired change?

Lilja_ · ‎06-04-2013

@zanyterp wrote:
No, they cannot be controlled/modified for the client. What is the desired change?

I would like to control it exactly as I can control the field-names in web-portal.
If I, as an example, would like to use LDAP credentials to trigger an OTP via SMS in a RADIUS server, the field name would say "Passcode" which is not what I want the user to see. It should in this case say "Password" or "Domain Password".

I can, on the other hand, use the RADIUS server as secondary authentication server and forward the credentials from my LDAP server (first authentication server) but then I will loose the security that a RADIUS server provides.

Any suggestions?

Kita_ · ‎06-04-2013

Hello Lilja,

This is possible, but not in a seamless fashion. All of the message (UI message, error message, etc) are pulled from local files existing on the end user machine. This means the modified files will need to be pushed to all Pulse clients through another mechanism outside of the SA device. This is not possible through any existing means within the SA device or Pulse client. Here are the locations to all of the files where Pulse messages are stored:

http://www.juniper.net/techpubs/en_US/junos-pulse2.1/topics/concepts/access-control-connect-error-me...

Specifically, the "PulseResource_*.txt" in the "C:\Program Files\Common Files\Juniper Networks\JamUI\" directory is where you will find the message for "Passcode" message. I have tested this in the lab by changing a few variables and this seems to work. However, this is not a fully supported solution and there is no guarntee this files will not change in the future. Please use at your own risk.