Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have set up a Cisco IPSec VPN connection instead of using the Cisco client on Mac OS X. I like it fairly well, it just sits in the tray next to the clock and allows me to easily connect and disconnect.

However, the one disadvantage to this is that Apple's network preference pane really enforces the remote server's policy of not storing user passwords, so it will let me store it once when I first create the connection, and it will let me connect with it that way, but after I disconnect it removes the password and won't let me type in that field anymore.

enter image description here

What I end up with is a box prompting me for login credentials each time I connect. Is there a way to bypass / auto fill this?

enter image description here

share|improve this question

3 Answers 3

up vote 2 down vote accepted

In the bad old days of using Cisco's client, it was easy to edit the .pcf file to work around the remote server policy. Using the alternative client Shimo has worked for me as of a couple of years ago (it's now closed-source, but you can get the old version from Google Code). Here's another workaround I haven't tried that uses the Keychain.

share|improve this answer
1  
Thank you. Cisco can be buggy on OS X though and so I much prefer the built in IPSec functionality. Yes with the pcf file you could store the password and make the file effectively "read only" so the client couldn't erase the password even if the remote server's policy said to do so. Also, Shimo might work but really my question is about how to do it on the built-in client. Have tried the workaround - it allows you to store the password initially but after you disconnect the password is erased. –  cwd Mar 5 '12 at 1:38

There is a workaround with AppleScript that works for me.

share|improve this answer
    
Can anyone confirm if this AppleScript still works in 10.9.4? I get my password pasted in the terminal if I run the script via osascript or pasted at the cursor if I run it from AppleScript Editor. –  cclark Jul 30 at 6:41
    
Yes it works on 10.9.4. You can also test my fork: gist.github.com/synox/c597321d6d007f812f45 –  Synox Sep 12 at 19:15
    
We ended up having it changed on the router to allow it to be saved so unfortunately I no longer have an environment where it is easy to test the fork. Thanks for following up and sharing. –  cclark Sep 16 at 4:25

I got another script on github.

Instead of simulating click and input, this script access the process and simply triggers the actions.

While the first time the script runs, OSX may ask for accessibility.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.