You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: _source/_posts/2025-01-21-terraform-powershell-lab.md
+51-51
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ You will save a private key alongside your code to simplify the lab. In producti
88
88
89
89
4. On your computer, paste the key into a file and save it as `key.pem`
90
90
91
-
**Important:** The key is saved locally to simplify the lab. You should save the key to an appropriate secrets management solution when working with production environments. If you do not have secrets management, [this blog post](/blog/2024/10/11/terraform-ci-cd) shares one way to set it up.
91
+
**Important:** The key is saved locally to simplify the lab. You should save the key to an appropriate secrets management solution when working with production environments. If you do not have secrets management, [this blog post](/blog/2024/10/11/terraform-ci-cd) shares one way to set it up.
92
92
93
93
5. Complete the configuration steps.
94
94
@@ -117,30 +117,30 @@ You will save a private key alongside your code to simplify the lab. In producti
@@ -202,23 +202,23 @@ You can access PowerShell 7 by launching it from the shortcut generated during i
202
202
4. Wait for the `terraform apply` to complete.
203
203
5. From the `Creation complete after` output, copy the value of the `okta_app_oauth` id.
204
204
205
-
**Note:** PowerShell and Terraform now have separate applications in your Okta organization. The PowerShell application's ID can also be found in the Okta admin console under Applications -> Applications.
205
+
**Note:** PowerShell and Terraform now have separate applications in your Okta organization. The PowerShell application's ID can also be found in the Okta admin console under Applications -> Applications.
206
206
207
207
6. In PowerShell, run these commands:
208
208
209
-
**Note:** Replace the {yourOktaDomain} with the entire domain for your Okta org. For example, `oktaice0000000.oktapreview.com`. Replace the ID with the value you copied above.
209
+
**Note:** Replace the {yourOktaDomain} with the entire domain for your Okta org. For example, `oktaice0000000.oktapreview.com`. Replace the ID with the value you copied above.
7. The `Invoke-OktaEstablishAccessToken` command displays a URL. Open the link in a web browser.
220
+
8. Authenticate to your Okta Training Org when prompted.
221
+
9. In your PowerShell session, run the command `Invoke-OktaListApplications`
222
222
223
223
## Extra Credit
224
224
You have set up the PowerShell application with various scopes. What interesting information about your organization can you retrieve using these scopes? Will these scopes allow you to make any changes to the Okta organization? Try some PowerShell commands to create or destroy resources and see what happens!
0 commit comments