Skip to content

Commit eb920e7

Browse files
committed
review fix
1 parent 49887d3 commit eb920e7

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

_source/_posts/2024-03-03-stepup-authentication.md

+8-4
Original file line numberDiff line numberDiff line change
@@ -136,11 +136,11 @@ It's clearer to see authentication strengths rather than calculate the recency o
136136

137137
## Set up authenticators
138138

139-
You'll change the Okta Admin Console to support a different authentication mechanism. We'll change the email authenticator so it's both a recovery and an authentication factor. Sign in to [your Okta Developer Edition Account](https://developer.okta.com/login) and press the **Admin Console** button.
139+
You'll change the Okta Admin Console to support a different authentication mechanism. We'll change the email authenticator so it's both a recovery and an authentication factor. Sign in to [your Okta Developer Edition Account](https://developer.okta.com/login).
140140

141141
Navigate to **Security** > **Authenticators**. Find **Email**, press on the **Actions** menu, and select **Edit**. Select the **Authentication and recovery** radio button under the **Used for** section.
142142

143-
Your Okta application should allow you to authenticate with a password or email.
143+
Your Okta application should allow you to authenticate with a password or email. Sign out of the Okta Admin Console so we can see the entire step-up authentication flow from end-to-end.
144144

145145
> **Note**
146146
>
@@ -161,7 +161,9 @@ Back to coding! The Okta Angular SDK supports step-up authentication and has a b
161161
}
162162
```
163163

164-
Test this route out. Start the application by running `npm start`. Open the application in the browser and sign in using one factor, such as a password. Then, navigate to the "profile" route. You'll get redirected to authenticate with Okta using your email. Sign in with your email by entering a verification number. Success!
164+
Test this route out. Start the application by running `npm start` if it isn't still running. Open the application in the browser, and feel free to open network debugging capabilities so you can see the `acr_values` request. Sign in using one factor, such as a password. Then, navigate to the "profile" route. You'll be redirected to Okta to authenticate using your email. Sign in with your email by entering a verification number. Success!
165+
166+
Sign out of the application.
165167

166168
The Okta Angular SDK helps us out, so we don't have to write custom code. Under the covers, the SDK has an Angular guard that:
167169
1. Gets the `acr` claim value from the ID token
@@ -401,7 +403,9 @@ public messages$ = this.http.get<Message[]>('/api/messages').pipe(
401403
);
402404
```
403405
404-
This code sure looks similar to the same operations as what the step-up auth Angular guard does!
406+
This code sure looks similar to the operations in the step-up auth Angular guard!
407+
408+
Try out your work. Ensure you sign out of the application first. Sign in with one factor, then navigate to the "messages" route. You'll redirect to sign in with a second factor. Success!
405409
406410
## Ensure authentication recency in step-up authentication
407411

0 commit comments

Comments
 (0)