@zanyterp, one can manually set the password on the credential stored on the token, but I'm not sure how I implied that manual generation of the credential would enable the Linux Pulse Secure client to use it. Why would manual generation make a difference? In any event, the client doesn't seem to know how to access the credential on the token (or if it does, I can't find any information on how to configure it to do so). I did see some info in the Pulse Secure client documentation on using certs that are stored in files, but one obviously can't do that with a hardware token by design. Am I overlooking something?
... View more
