Forum Discussion
Mandatory AccessKey parameter for Import-WACConnection Powershell cmdlet in 2410
Hello Ma-Po!
With the new version of Admin Center, they’ve added the AccessKey parameter for extra security when using the Import-WACConnection cmdlet. Since you're using Kerberos authentication, you don’t normally need an access key, but with this update, it's required.
To find the AccessKey, go to the Windows Admin Center UI, then navigate to the "Settings" menu, and in the "General" section, you should see an option to generate an AccessKey under "Authentication." If you can’t find it there, it could be related to a setting in your WAC deployment or version. If it's still not showing up, I recommend checking if there's a new update or patch for Admin Center that may resolve this issue.
I hope it helps!
I think luchete is missing the point.
Ma-Po Highlighted that his requirement (which mine is too) that an import needs to happen on schedule/automatically. This will keeps the list of connections in WAC updated.The current solution of generating an AccessKey (Found in Settings => Under Gateway Tree on left => Reveal Access Key (Checkbox) must be manually done and can't be automated. Which means this becomes a manual process.
Unlike many WebUI apps these days, there doesn't appear to be any way of generating a API token that works long term for the purposes of automation like I described above.
This should be a builtin feature in which the WAC admin can generate an API token and use for exactly this type of purpose.
