113 connection to jamf pro should be updated to use bearer tokens #114
Conversation
…eing a valid type to use for our purposes.
…e and make a unit test for it.
…files for better consistency.
|
If anybody can tell me what exactly SwiftLint is complaining about with the 6 |
… of comments in URLSessionAsyncCompatibility.
|
I updated the GitHub action that runs SwiftLint to the latest version, modified a couple of comments in the code, and now it's happy. |
There was a problem hiding this comment.
@macblazer nice to see the async await changes and I think they all look great.
I did notice one issue in testing, which was an error "Jamf Pro Server is unavailable" when I tried an earlier version of Jamf Pro (10.21.0). This happened during the "Check Connection" button pressed.
Not sure which version cutoff it was for bearer tokens, but if you can double check how far back we want to support for Jamf Pro.
…c authorization. Added unit tests of the NetworkAuthManager code.
Refactored some of the code around the networking, such as making a
SemanticVersiontype and moving the configuration profile API payload generation out of the networking code and over to theTCCProfiletype.Using async-await style network connections, and using an
actorto synchronize getting/refreshing a bearer token.Fixes #113