Automatic input of user credentials for 802.1X authentication on Windows 10 via registry The...

The phrase "to the numbers born"?

How much of the clove should I use when using big garlic heads?

Why couldn't they take pictures of a closer black hole?

How can I have a shield and a way of attacking with a ranged weapon at the same time?

What is the meaning of Triage in Cybersec world?

Pokemon Turn Based battle (Python)

writing variables above the numbers in tikz picture

Can we generate random numbers using irrational numbers like π and e?

What is this business jet?

Why are there uneven bright areas in this photo of black hole?

Is it safe to harvest rainwater that fell on solar panels?

For what reasons would an animal species NOT cross a *horizontal* land bridge?

What is the most efficient way to store a numeric range?

Falsification in Math vs Science

Kerning for subscripts of sigma?

Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?

Does adding complexity mean a more secure cipher?

How come people say “Would of”?

Why doesn't shell automatically fix "useless use of cat"?

Dropping list elements from nested list after evaluation

How to obtain a position of last non-zero element

Can a flute soloist sit?

How to quickly solve partial fractions equation?

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?



Automatic input of user credentials for 802.1X authentication on Windows 10 via registry



The 2019 Stack Overflow Developer Survey Results Are InRegistry entry for User Authentication?In Windows 7 Where/what are (if any) the settings that bypass the switch user screen and go directly to the authenication screen?Hang when launching digitally signed executablePowershell possible to give input to underlying scriptPossible registry fix for a “Not enough memory to run Microsoft excel” errorIs there any way to control “Device Installation Restrictions” via the Registry (instead of Group Policy) for users on Windows Home Editions?Configuring 802.1x PEAP credentials wireless Wi-Fi with PowerShellUnified Write Filter with WPA2-Enterprise PEAP-MSCHAPv2How to disable single click to open files and folders? (GUI appears disabled)Registry auditing for disconnected users





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I want to automate the configuration settings which are needed in our 802.1X environment. For this I need to pass user credentials.



Therefore I want to build a small GUI which expects the user credentials. After a click on something like a logon button, a powershell script shall import a xml file which contains configuration data for the network interface.



This XML will be imported with:



netsh lan add profile filename="PATH_AND_FILENAME.xml" interface="INTERFACE_NAME"



After this is done I want to pass the user credentials (which were given in the GUI) to the OS without using the built in dialog.



I found out that the registry entries which store the credentials are something like:



User HKCUSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



and



Machine HKLMSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



but these are for wireless connections.



Does anyone know the correct registry entry?










share|improve this question









New contributor




Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



























    0















    I want to automate the configuration settings which are needed in our 802.1X environment. For this I need to pass user credentials.



    Therefore I want to build a small GUI which expects the user credentials. After a click on something like a logon button, a powershell script shall import a xml file which contains configuration data for the network interface.



    This XML will be imported with:



    netsh lan add profile filename="PATH_AND_FILENAME.xml" interface="INTERFACE_NAME"



    After this is done I want to pass the user credentials (which were given in the GUI) to the OS without using the built in dialog.



    I found out that the registry entries which store the credentials are something like:



    User HKCUSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



    and



    Machine HKLMSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



    but these are for wireless connections.



    Does anyone know the correct registry entry?










    share|improve this question









    New contributor




    Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I want to automate the configuration settings which are needed in our 802.1X environment. For this I need to pass user credentials.



      Therefore I want to build a small GUI which expects the user credentials. After a click on something like a logon button, a powershell script shall import a xml file which contains configuration data for the network interface.



      This XML will be imported with:



      netsh lan add profile filename="PATH_AND_FILENAME.xml" interface="INTERFACE_NAME"



      After this is done I want to pass the user credentials (which were given in the GUI) to the OS without using the built in dialog.



      I found out that the registry entries which store the credentials are something like:



      User HKCUSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



      and



      Machine HKLMSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



      but these are for wireless connections.



      Does anyone know the correct registry entry?










      share|improve this question









      New contributor




      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I want to automate the configuration settings which are needed in our 802.1X environment. For this I need to pass user credentials.



      Therefore I want to build a small GUI which expects the user credentials. After a click on something like a logon button, a powershell script shall import a xml file which contains configuration data for the network interface.



      This XML will be imported with:



      netsh lan add profile filename="PATH_AND_FILENAME.xml" interface="INTERFACE_NAME"



      After this is done I want to pass the user credentials (which were given in the GUI) to the OS without using the built in dialog.



      I found out that the registry entries which store the credentials are something like:



      User HKCUSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



      and



      Machine HKLMSoftwareMicrosoftWlansvcUserDataProfiles[GUID]



      but these are for wireless connections.



      Does anyone know the correct registry entry?







      windows-10 powershell windows-registry






      share|improve this question









      New contributor




      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited yesterday









      Ola Ström

      1767




      1767






      New contributor




      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked yesterday









      Andi D.Andi D.

      13




      13




      New contributor




      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Andi D. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Trying o pull user creds is not prudent. There are not there in plain text and are not reversible for passing on to any other action.



          You say you are presenting a GUI to ask the user for creds. During any interactive session, if you asking for creds, you need to ask for them securely.



          Once you've done that, you can get the username and password directly via code. Yet, you are now handling very sensitive user information. You really need to check with your security / risk management / policy team about doing this. This is because you are literally capturing user creds that you can use anywhere the user has access and nothing prevents you from running off with them later.



          So, you could simply use Get-Credential or create a new PSCredential object, or use SecureString to ask for user creds, then when you need them, just reverse that.



          ($Creds = Get-credential -Credential "$env:USERDOMAIN$env:USERDOMAIN")

          $Creds.GetNetworkCredential().UserName
          $Creds.GetNetworkCredential().Password

          # Results

          UserName Password
          -------- --------
          contosotestuser System.Security.SecureString
          testuser
          password



          ($Username = Read-Host -Prompt 'Enter username')
          ($Password = Read-Host -Prompt 'Enter password' -AsSecureString)
          ($Creds = New-Object System.Management.Automation.PSCredential ($Username, $Password))

          $Creds.GetNetworkCredential().UserName
          $Creds.GetNetworkCredential().Password

          # Results

          Enter username: contosotestuser
          contosotestuser
          System.Security.SecureString

          UserName Password
          -------- --------
          contosotestuser System.Security.SecureString
          testuser
          password


          ($Creds = New-Object PSCredential $Username, $Password)

          $Creds.GetNetworkCredential().UserName
          $Creds.GetNetworkCredential().Password


          # Results

          $Creds

          UserName Password
          -------- --------
          contosotestuser System.Security.SecureString

          UserName Password
          -------- --------
          contosotestuser System.Security.SecureString
          testuser
          password





          share|improve this answer
























            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
            });


            }
            });






            Andi D. is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1423763%2fautomatic-input-of-user-credentials-for-802-1x-authentication-on-windows-10-via%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









            0














            Trying o pull user creds is not prudent. There are not there in plain text and are not reversible for passing on to any other action.



            You say you are presenting a GUI to ask the user for creds. During any interactive session, if you asking for creds, you need to ask for them securely.



            Once you've done that, you can get the username and password directly via code. Yet, you are now handling very sensitive user information. You really need to check with your security / risk management / policy team about doing this. This is because you are literally capturing user creds that you can use anywhere the user has access and nothing prevents you from running off with them later.



            So, you could simply use Get-Credential or create a new PSCredential object, or use SecureString to ask for user creds, then when you need them, just reverse that.



            ($Creds = Get-credential -Credential "$env:USERDOMAIN$env:USERDOMAIN")

            $Creds.GetNetworkCredential().UserName
            $Creds.GetNetworkCredential().Password

            # Results

            UserName Password
            -------- --------
            contosotestuser System.Security.SecureString
            testuser
            password



            ($Username = Read-Host -Prompt 'Enter username')
            ($Password = Read-Host -Prompt 'Enter password' -AsSecureString)
            ($Creds = New-Object System.Management.Automation.PSCredential ($Username, $Password))

            $Creds.GetNetworkCredential().UserName
            $Creds.GetNetworkCredential().Password

            # Results

            Enter username: contosotestuser
            contosotestuser
            System.Security.SecureString

            UserName Password
            -------- --------
            contosotestuser System.Security.SecureString
            testuser
            password


            ($Creds = New-Object PSCredential $Username, $Password)

            $Creds.GetNetworkCredential().UserName
            $Creds.GetNetworkCredential().Password


            # Results

            $Creds

            UserName Password
            -------- --------
            contosotestuser System.Security.SecureString

            UserName Password
            -------- --------
            contosotestuser System.Security.SecureString
            testuser
            password





            share|improve this answer




























              0














              Trying o pull user creds is not prudent. There are not there in plain text and are not reversible for passing on to any other action.



              You say you are presenting a GUI to ask the user for creds. During any interactive session, if you asking for creds, you need to ask for them securely.



              Once you've done that, you can get the username and password directly via code. Yet, you are now handling very sensitive user information. You really need to check with your security / risk management / policy team about doing this. This is because you are literally capturing user creds that you can use anywhere the user has access and nothing prevents you from running off with them later.



              So, you could simply use Get-Credential or create a new PSCredential object, or use SecureString to ask for user creds, then when you need them, just reverse that.



              ($Creds = Get-credential -Credential "$env:USERDOMAIN$env:USERDOMAIN")

              $Creds.GetNetworkCredential().UserName
              $Creds.GetNetworkCredential().Password

              # Results

              UserName Password
              -------- --------
              contosotestuser System.Security.SecureString
              testuser
              password



              ($Username = Read-Host -Prompt 'Enter username')
              ($Password = Read-Host -Prompt 'Enter password' -AsSecureString)
              ($Creds = New-Object System.Management.Automation.PSCredential ($Username, $Password))

              $Creds.GetNetworkCredential().UserName
              $Creds.GetNetworkCredential().Password

              # Results

              Enter username: contosotestuser
              contosotestuser
              System.Security.SecureString

              UserName Password
              -------- --------
              contosotestuser System.Security.SecureString
              testuser
              password


              ($Creds = New-Object PSCredential $Username, $Password)

              $Creds.GetNetworkCredential().UserName
              $Creds.GetNetworkCredential().Password


              # Results

              $Creds

              UserName Password
              -------- --------
              contosotestuser System.Security.SecureString

              UserName Password
              -------- --------
              contosotestuser System.Security.SecureString
              testuser
              password





              share|improve this answer


























                0












                0








                0







                Trying o pull user creds is not prudent. There are not there in plain text and are not reversible for passing on to any other action.



                You say you are presenting a GUI to ask the user for creds. During any interactive session, if you asking for creds, you need to ask for them securely.



                Once you've done that, you can get the username and password directly via code. Yet, you are now handling very sensitive user information. You really need to check with your security / risk management / policy team about doing this. This is because you are literally capturing user creds that you can use anywhere the user has access and nothing prevents you from running off with them later.



                So, you could simply use Get-Credential or create a new PSCredential object, or use SecureString to ask for user creds, then when you need them, just reverse that.



                ($Creds = Get-credential -Credential "$env:USERDOMAIN$env:USERDOMAIN")

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password

                # Results

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password



                ($Username = Read-Host -Prompt 'Enter username')
                ($Password = Read-Host -Prompt 'Enter password' -AsSecureString)
                ($Creds = New-Object System.Management.Automation.PSCredential ($Username, $Password))

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password

                # Results

                Enter username: contosotestuser
                contosotestuser
                System.Security.SecureString

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password


                ($Creds = New-Object PSCredential $Username, $Password)

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password


                # Results

                $Creds

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password





                share|improve this answer













                Trying o pull user creds is not prudent. There are not there in plain text and are not reversible for passing on to any other action.



                You say you are presenting a GUI to ask the user for creds. During any interactive session, if you asking for creds, you need to ask for them securely.



                Once you've done that, you can get the username and password directly via code. Yet, you are now handling very sensitive user information. You really need to check with your security / risk management / policy team about doing this. This is because you are literally capturing user creds that you can use anywhere the user has access and nothing prevents you from running off with them later.



                So, you could simply use Get-Credential or create a new PSCredential object, or use SecureString to ask for user creds, then when you need them, just reverse that.



                ($Creds = Get-credential -Credential "$env:USERDOMAIN$env:USERDOMAIN")

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password

                # Results

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password



                ($Username = Read-Host -Prompt 'Enter username')
                ($Password = Read-Host -Prompt 'Enter password' -AsSecureString)
                ($Creds = New-Object System.Management.Automation.PSCredential ($Username, $Password))

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password

                # Results

                Enter username: contosotestuser
                contosotestuser
                System.Security.SecureString

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password


                ($Creds = New-Object PSCredential $Username, $Password)

                $Creds.GetNetworkCredential().UserName
                $Creds.GetNetworkCredential().Password


                # Results

                $Creds

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString

                UserName Password
                -------- --------
                contosotestuser System.Security.SecureString
                testuser
                password






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                postanotepostanote

                1,153133




                1,153133






















                    Andi D. is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    Andi D. is a new contributor. Be nice, and check out our Code of Conduct.













                    Andi D. is a new contributor. Be nice, and check out our Code of Conduct.












                    Andi D. is a new contributor. Be nice, and check out our Code of Conduct.
















                    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%2f1423763%2fautomatic-input-of-user-credentials-for-802-1x-authentication-on-windows-10-via%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

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                    looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...