Junos Pulse 3.0 on Microsoft Windows supports Credential Provider for Windows Vista and Windows 7. It provides a mechanism for establishing a network tunnel upon login to the Windows device, ensuring corporate network connectivity during critical login processes. The Junos Pulse Credential Provider has been implemented as a Pre-Logon Access Provider (PLAP). Junos Pulse provides Credential Provider support for remote SSL VPN access, as well as for Layer 3 Juniper UAC access.
Will Junos pulse cache a new set of credentials? Had issue with NC where only valid credentials would work. I want to use Pulse PLAP to fix password issues remote.
forget it I answered my own question. YES it does. I can cache a entire new ID had to setup pulse on VPN but it works great
Has anyone else run into trouble with this? I see the tile, the connection is established (see it on the SA, IP assigned etc.) but the Windows login process (Windows 7 Professional) remains in the "Pulse is connecting to X" screen with a cancel button, and never proceeds to actually log the user in. Policy tracing suggests things are going just fine, session created, roles mapped etc.
Incidentally, as far as I can tell, the user must select "switch user" to see the Pulse tile. Even if the option to start as part of the login process is selected if the user just uses the Windows default of the previously logged in user, the VPN never triggers. Is there a way to work around that?
I do. And as said, it doesn't return an error; the input boxes go away, and it just sits there without getting to the desktop.
(Aside from the user confusion factor of having the same prompt for different credentials.)
Just to add: The System log, Application log and Security log on the system show no entries at all corresponding to the login attempt. That's windows logging for you, I suppose. They show my previous and subsequent logins using the user tile, rather than the Pulse tile.