Release Notes
Release Highlights¶
Note From the Team
Just before the summer heat kicks off in Arizona, we've wrapped up adding support for configuring 8021x in AMT using RPC-Go. With this milestone, we're nearing the completion of all the major features planned in RPC-Go for Enterprise support MVP release. That being said, we've also been looking at how to address the gap created by MeshCommander’s end of support for our Enterprise customers. The team has been hard at work architecting and developing an alternative for a 1:1 Console application for enterprise-style networks.
Development is still pretty early, but the team is progressing steadily. You can follow the progress in our Console GitHub Repo. Stay tuned for updates soon!
Best Wishes,
The Open AMT Cloud Toolkit Team
What's New?¶
Feature: RPC-Go Local Wired 802.1x Configuration
The configure wired
command now supports configuration of AMT for wired 802.1x environments. By providing the Enterprise Assistant (EA) credentials, RPC-Go can communicate securely with EA and perform the configuration. Configuration info can be passed various ways, such as directly via the command line, read from a config file, or passed as a JSON string.
See the rpc configure wired
documentation for additional details and examples.
rpc configure wired -config config.yaml
password: 'AMTPassword' # alternatively, you can provide the AMT password of the device in the command line
wiredConfig:
dhcp: true
ipsync: true
ieee8021xProfileName: 'exampleIeee8021xEAP-TLS'
enterpriseAssistant:
eaAddress: 'http://<YOUR-IPADDRESS-OR-FQDN>:8000'
eaUsername: 'eaUser'
eaPassword: 'eaPass'
ieee8021xConfigs:
- profileName: 'exampleIeee8021xEAP-TLS'
authenticationProtocol: 0
Feature: RPC-Go Local Wireless 802.1x Configuration
Previously, we only allowed users to directly pass in the certificates and secrets themselves on the command line. Now, just like for wired configurations, you can use Enterprise Assistant to communicate to the Microsoft CA and issue certificates to AMT. Configuration info can be passed various ways, such as directly via the command line, read from a config file, or passed as a JSON string.
See the rpc configure wireless
command documentation for additional details and examples.
rpc configure wireless -config config.yaml
password: 'AMTPassword' # alternatively, you can provide the AMT password of the device in the command line
enterpriseAssistant:
eaAddress: 'http://<YOUR-IPADDRESS-OR-FQDN>:8000'
eaUsername: 'eaUser'
eaPassword: 'eaPass'
wifiConfigs:
- profileName: 'exampleWifi8021x' # friendly name (ex. Profile name)
ssid: 'ssid'
priority: 1
authenticationMethod: 7
encryptionMethod: 4
ieee8021xProfileName: 'exampleIeee8021xEAP-TLS'
ieee8021xConfigs:
- profileName: 'exampleIeee8021xEAP-TLS'
authenticationProtocol: 0 #8021x profile (ex. EAP-TLS(0))
Feature: RPC-Go Configure TLS using a Config File
Configuring TLS now supports using a config .yaml
/.json
file. Now, you can provide the details and configure TLS at the same time as activation and network configuration all within the same config file.
See the rpc configure tls
command documentation for additional details and examples.
rpc configure tls -config config.yaml
password: 'AMTPassword' # alternatively, you can provide the AMT password of the device in the command line
tlsConfig:
mode: 'Server'
enterpriseAssistant:
eaAddress: 'http://<YOUR-IPADDRESS-OR-FQDN>:8000'
eaUsername: 'eaUser'
eaPassword: 'eaPass'
Get the Details¶
Additions, Modifications, and Removals¶
RPS¶
v2.22.5
RPC-Go¶
v2.34.1
v2.34.0
- feat: add yaml support to local tls config (8ecb612)
v2.33.1
- fix: 8021x wifi config with preexisting root cert (55cc329)
- fix: return value on success in lib.go (#499) (ea30d19)
v2.33.0
- feat: adds 8021x to wired configuration (1e34d85)
-
fix: changes amtinfo output to use stdout instead of stderr (7caa756)
v2.32.2
- fix: read ccm password from commandline (5a83d49)
Enterprise Assistant (EA)¶
Note
Enterprise Assistant will soon begin to have tagged releases. We will share an official announcement when the first tagged release becomes available.
- fix: update security key length #21
go-wsman-messages¶
v2.5.0
v2.4.1
v2.4.0
v2.3.2
v2.3.1
v2.3.0
v2.2.4
v2.2.3
Project Boards¶
Check out our new Sprint Planning project board to see what stories the dev team is actively working on, what is in our backlog, and what is planned for the next sprint.