Mac OS X asks for Admin Username and Password twice before allowing access to Cisco AnyConnect VPN












8















OS X asks me -- twice -- to enter my admin username and password before it will let me connect to Cisco AnyConnect VPN. This is annoying and unnecessary.



Text of the prompt:




OS X wants to make changes. Type an administrator's name and password to allow this.



OS X wants to use the "System" keychain.




OS X wants to make changes



How can I configure the keychain to allow Cisco VPN access without prompting unnecessarily?










share|improve this question





























    8















    OS X asks me -- twice -- to enter my admin username and password before it will let me connect to Cisco AnyConnect VPN. This is annoying and unnecessary.



    Text of the prompt:




    OS X wants to make changes. Type an administrator's name and password to allow this.



    OS X wants to use the "System" keychain.




    OS X wants to make changes



    How can I configure the keychain to allow Cisco VPN access without prompting unnecessarily?










    share|improve this question



























      8












      8








      8


      4






      OS X asks me -- twice -- to enter my admin username and password before it will let me connect to Cisco AnyConnect VPN. This is annoying and unnecessary.



      Text of the prompt:




      OS X wants to make changes. Type an administrator's name and password to allow this.



      OS X wants to use the "System" keychain.




      OS X wants to make changes



      How can I configure the keychain to allow Cisco VPN access without prompting unnecessarily?










      share|improve this question
















      OS X asks me -- twice -- to enter my admin username and password before it will let me connect to Cisco AnyConnect VPN. This is annoying and unnecessary.



      Text of the prompt:




      OS X wants to make changes. Type an administrator's name and password to allow this.



      OS X wants to use the "System" keychain.




      OS X wants to make changes



      How can I configure the keychain to allow Cisco VPN access without prompting unnecessarily?







      macos vpn passwords cisco-vpn-client cisco-anyconnect






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 14 at 13:33









      steoleary

      1034




      1034










      asked Mar 22 '18 at 17:49









      Jake TorontoJake Toronto

      22127




      22127






















          1 Answer
          1






          active

          oldest

          votes


















          8














          Found the answer on a Google Groups forum:




          • Launch /Applications/Utilities/Keychain Access



          • Select "System" from the Keychains menu in the upper left



          • Select "Certificates" from the Category menu in the lower left



          • Find the entry that corelates to your computer's name in the list on the right, and click on the disclosure triangle.



          • Secondary click on the "Private Key" entry that appears and select "Get Info" from the contextual menu that appears.



          • Select the Access Control tab.



          • You can then either add AnyConnect to the the list at the bottom of the screen (more secure, but you will need to repeat this process anytime the version of AnyConnect changes), or toggle the radio button to "Allow all applications to access this item".




          A similar answer shows a picture but provides fewer instructions






          share|improve this answer
























          • I've looking for this answer for ages! Thanks 🙏

            – raed
            Jul 13 '18 at 8:39











          • This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

            – Marco
            Dec 1 '18 at 7:22












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1306893%2fmac-os-x-asks-for-admin-username-and-password-twice-before-allowing-access-to-ci%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          8














          Found the answer on a Google Groups forum:




          • Launch /Applications/Utilities/Keychain Access



          • Select "System" from the Keychains menu in the upper left



          • Select "Certificates" from the Category menu in the lower left



          • Find the entry that corelates to your computer's name in the list on the right, and click on the disclosure triangle.



          • Secondary click on the "Private Key" entry that appears and select "Get Info" from the contextual menu that appears.



          • Select the Access Control tab.



          • You can then either add AnyConnect to the the list at the bottom of the screen (more secure, but you will need to repeat this process anytime the version of AnyConnect changes), or toggle the radio button to "Allow all applications to access this item".




          A similar answer shows a picture but provides fewer instructions






          share|improve this answer
























          • I've looking for this answer for ages! Thanks 🙏

            – raed
            Jul 13 '18 at 8:39











          • This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

            – Marco
            Dec 1 '18 at 7:22
















          8














          Found the answer on a Google Groups forum:




          • Launch /Applications/Utilities/Keychain Access



          • Select "System" from the Keychains menu in the upper left



          • Select "Certificates" from the Category menu in the lower left



          • Find the entry that corelates to your computer's name in the list on the right, and click on the disclosure triangle.



          • Secondary click on the "Private Key" entry that appears and select "Get Info" from the contextual menu that appears.



          • Select the Access Control tab.



          • You can then either add AnyConnect to the the list at the bottom of the screen (more secure, but you will need to repeat this process anytime the version of AnyConnect changes), or toggle the radio button to "Allow all applications to access this item".




          A similar answer shows a picture but provides fewer instructions






          share|improve this answer
























          • I've looking for this answer for ages! Thanks 🙏

            – raed
            Jul 13 '18 at 8:39











          • This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

            – Marco
            Dec 1 '18 at 7:22














          8












          8








          8







          Found the answer on a Google Groups forum:




          • Launch /Applications/Utilities/Keychain Access



          • Select "System" from the Keychains menu in the upper left



          • Select "Certificates" from the Category menu in the lower left



          • Find the entry that corelates to your computer's name in the list on the right, and click on the disclosure triangle.



          • Secondary click on the "Private Key" entry that appears and select "Get Info" from the contextual menu that appears.



          • Select the Access Control tab.



          • You can then either add AnyConnect to the the list at the bottom of the screen (more secure, but you will need to repeat this process anytime the version of AnyConnect changes), or toggle the radio button to "Allow all applications to access this item".




          A similar answer shows a picture but provides fewer instructions






          share|improve this answer













          Found the answer on a Google Groups forum:




          • Launch /Applications/Utilities/Keychain Access



          • Select "System" from the Keychains menu in the upper left



          • Select "Certificates" from the Category menu in the lower left



          • Find the entry that corelates to your computer's name in the list on the right, and click on the disclosure triangle.



          • Secondary click on the "Private Key" entry that appears and select "Get Info" from the contextual menu that appears.



          • Select the Access Control tab.



          • You can then either add AnyConnect to the the list at the bottom of the screen (more secure, but you will need to repeat this process anytime the version of AnyConnect changes), or toggle the radio button to "Allow all applications to access this item".




          A similar answer shows a picture but provides fewer instructions







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 22 '18 at 17:49









          Jake TorontoJake Toronto

          22127




          22127













          • I've looking for this answer for ages! Thanks 🙏

            – raed
            Jul 13 '18 at 8:39











          • This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

            – Marco
            Dec 1 '18 at 7:22



















          • I've looking for this answer for ages! Thanks 🙏

            – raed
            Jul 13 '18 at 8:39











          • This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

            – Marco
            Dec 1 '18 at 7:22

















          I've looking for this answer for ages! Thanks 🙏

          – raed
          Jul 13 '18 at 8:39





          I've looking for this answer for ages! Thanks 🙏

          – raed
          Jul 13 '18 at 8:39













          This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

          – Marco
          Dec 1 '18 at 7:22





          This was very useful in pointing me to the right spot; however, for others who may be getting here, the "entry that correlates to your computer's name" was not what worked for me: in my case, adding AnyConnect to the localhost entry did not fix the issue; what did, was adding it to a seeming "random hex" entry.

          – Marco
          Dec 1 '18 at 7:22


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1306893%2fmac-os-x-asks-for-admin-username-and-password-twice-before-allowing-access-to-ci%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕