Skip to content

Commit ead1053

Browse files
links open in separate tab now
1 parent 7bd8519 commit ead1053

File tree

1 file changed

+10
-10
lines changed
  • packages/@okta/vuepress-site/docs/guides/manage-user-creds/main

1 file changed

+10
-10
lines changed

packages/@okta/vuepress-site/docs/guides/manage-user-creds/main/index.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ meta:
55
content: Learn about how to securely manage user credentials using the Okta Client SDK.
66
---
77

8-
Securely manage your tokens using the Okta Client SDK, which provides a robust token management system designed to handle complex scenarios.
8+
Securely manage your tokens using the Okta JavaScript Client SDK, which provides a robust token management system designed to handle complex scenarios.
99

1010
---
1111

@@ -18,7 +18,7 @@ Securely manage your tokens using the Okta Client SDK, which provides a robust t
1818

1919
#### What you need
2020

21-
[The Okta Client SDK configured for your app](link to SDK)
21+
[The Okta JavaScript Client SDK configured for your app](link to SDK)
2222

2323
---
2424

@@ -33,7 +33,7 @@ After the user (or other identity) is authenticated within an app, you must mana
3333
* Ensure that it's correctly refreshed as required.
3434
* Remove it after reaching expiration or a direct deletion request.
3535

36-
The Okta Client SDK provides a robust token management system designed to handle complex scenarios, such as multi-threaded access and data race conditions. This allows you to focus on your app's features rather than building a complex token management system from scratch.
36+
The Okta JavaScript Client SDK provides a robust token management system designed to handle complex scenarios, such as multi-threaded access and data race conditions. This allows you to focus on your app's features rather than building a complex token management system from scratch.
3737

3838
### Okta Client SDK design principles
3939

@@ -209,12 +209,12 @@ When a user signs out or a session needs to be terminated, it's critical to prop
209209
210210
Use the following key recommendations for secure token management:
211211
212-
* Always use the [Authorization Code Flow with PKCE](/docs/guides/implement-grant-type/authcodepkce/main/).
213-
* Use [short-lived access tokens](/docs/guides/oie-embedded-common-refresh-tokens/-/main/).
214-
* Use and rotate [refresh tokens](/docs/guides/refresh-tokens/main/#refresh-token-rotation).
212+
* Always use the <a href="https://developer.okta.com/docs/guides/implement-grant-type/authcodepkce/main/" target="_blank">Authorization Code Flow with PKCE</a>.
213+
* Use <a href="https://developer.okta.com/docs/guides/oie-embedded-common-refresh-tokens/-/main/" target="_blank">short-lived access tokens</a>.
214+
* Use and rotate <a href="https://developer.okta.com/docs/guides/refresh-tokens/main/#refresh-token-rotation/" target="_blank">refresh tokens</a>.
215215
* Implement robust XSS and CSRF protections.
216-
* Always [revoke tokens](/docs/guides/revoke-tokens/main/) when a user signs out.
217-
* Register a [custom domain URL for your Okta org](/docs/guides/custom-url-domain/main/) to unlock branding capabilities and simplify session management.
216+
* Always <a href="https://developer.okta.com/docs/guides/revoke-tokens/main/" target="_blank">revoke tokens</a> when a user signs out.
217+
* Register a <a href="https://developer.okta.com/docs/guides/custom-url-domain/main/" target="_blank">custom domain URL for your Okta org</a> to unlock branding capabilities and simplify session management.
218218
* To mitigate risk and ensure proper access token use:
219-
* Configure APIs with specific [authorization server](/docs/guides/customize-authz-server/main/) audiences, for example, `api.company.com/product1` instead of the base `api.company.com`.
220-
* Use [granular scopes](/docs/guides/customize-authz-server/main/#create-scopes), for example, `com.okta.product1.admin` instead of a generic administrator scope.
219+
* Configure APIs with specific <a href="https://developer.okta.com/docs/guides/customize-authz-server/main/" target="_blank">authorization server</a> audiences, for example, `api.company.com/product1` instead of the base `api.company.com`.
220+
* Use <a href="https://developer.okta.com/docs/guides/customize-authz-server/main/#create-scopes" target="_blank">granular scopes</a>, for example, `com.okta.product1.admin` instead of a generic administrator scope.

0 commit comments

Comments
 (0)