How would I need to configure the access policy for this to work? I tried with and without a logon page, but I don't seem to be getting a username and/or password passed through from the client, none of the session variables show the values from the edge client config file. I guess I would need to set the connectivity profile to allow password caching and save it to disk, but can I make that change, download the package with those options, and then change it back as we generally don't want the passwords to be cached? The svpn and policyserver components of the F5 BIG-IP APM client prior to version 7.1.7.1 for Linux and macOS ran as a privileged process and could allow an unprivileged user to get ownership of files owned by root on the local client host. Even if I edit the file and save it, it just ignores the password I put in there and removes it afterwards.
I went back and checked my F5 settings, and sure enough the save password on exit setting is set to false. I keep getting authentication failures, and when I check the client.f5c, I see that it has not saved my password. This needs to be done in the background as it is using straight username and password authentication and we don't want the users to see that. To briefly summarize, this is for a remote password self-service application, so I need for the client machines to be able to do a remote command line access using "f5fpc -start /c "C:\Program Files\F5 VPN\client.f5c /t /q" so the users don't get any prompts or pop-ups, the client.f5c file has to provide the username and password and server to connect to, then the password self service app does its thing, and finally issues the command "f5fpc -stop" at the end to close the VPN session out. I am trying to get our F5 11.4 APM set up to work with remote Windows clients that need to connect and then disconnect from the VPN without any user interaction.