Ramblings of a Tinkerer

Okta is updating their identity platform and moving away from the Okta Classic Engine to the Okta Identity Engine. With this update, the way that Device Trust is configured has completely changed. The updated device trust now relies upon the MDM deployment of the Okta Verify app deployed with a specific Application Configuration containing a key generated from the Okta console. If the key from the console matches the key stored in the app on the device, the device must be enrolled (otherwise, how would it have received the matching key) and the device is considered trusted. Add Okta Verify as an authenticator In the Okta console, go to Security > Authenticators Under Setup , click Add Authenticator Select Okta Verify and configure the required options Create an enrollment policy (or edit the default) In the Admin console, to go Security > Authenticators Under Enrollment , add a new policy (or edit an existing one) In the Eligible Authenticators section , select one of the fo...

PowerShell. That thing that replaced the Command terminal (or if you're old enough to remember, DOS) on Windows, is actually cross platform and can be run on a number of other O/S's including macOS. If you're a macOS user and you work with customers who primarily use Windows, PowerShell is a great way to build out script that they can use and is very useful when it comes to using API's. I've done a lot of work with the Workspace ONE API's in the past and thought it it would be worth making a post on how to use PowerShell on your mac as well as some samples that you can use to call the Workspace ONE API's X Code Install (Required for Homebrew) Terminal command: Xcode-select –install (If prompted, install the Command Line Developer tools) Homebrew Install (Required to Install PowerShell) Terminal Command (To download Homebrew):  curl -fsSL -o install.sh https://raw.githubusercontent.com/Homebrew/install/master/install.sh Terminal Command (To installs Homebrew)...