All Topics » Pulse Policy Secure

Junos Pulse Help

Contributor (11)
Apr 18, 2014 12:24pm



we are tyring to deploy 8021.x layer 2 authentication with junos pulse to users desktop.


one of the problems we are running into is user experiences with the fact that junos pulse sometimes pop up to do the ldap authentication and non technical users are not comfortable with authenticating and click okay.


is there any way to make junos pulse run in the back so that users won't notice?


also, is there anyway to update all junos pulses in the field from a central location? or any server we can use to make this process easy?



any advie is greatly appreciated.



Thank you, 

Contributor (11)
Apr 21, 2014 5:19am

Are the users saving the credenatial during the initial login ? If not can you try that see if that is helping here. Other than this I am not sure what exactly you have in mind when you said running pulse in the back. Can you ellobrate ?


When does the user authentication pop-up happens ? Can you check whether the pop-up is due to timeouts either from the L2 switch or on IC role session option etc ?


Also here is the Pulse documentation around installation that could help here as well.

    Contributor (11)
    Apr 23, 2014 12:29pm



    Thank your for your reply.


    I am thinking to do is to hide junos pulse process. even the users authentication fails, i don't want it to pop up.


    the problem is whatever happens to the pc, users think junos pulse is doing. for example, even when the password is expired, non technical users open tickets aganist junos pulse , which is funny. so i am thinking if we can hide the junos pulse from day one, uses won't be as confused and we can solve the problems when there is a real junos pulse related problems.



    Thank you