Skip to content

Commit d8edaf1

Browse files
Merge pull request #4176 from okta/sdh-okta599051-removeRN
remove rn per doc action
2 parents c1e5b2f + acb6c18 commit d8edaf1

File tree

2 files changed

+6
-10
lines changed
  • packages/@okta/vuepress-site/docs/release-notes

2 files changed

+6
-10
lines changed

packages/@okta/vuepress-site/docs/release-notes/2023-okta-identity-engine/index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ title: Okta Identity Engine API Products release notes 2023
1212
| ------ | ------------------------ |
1313
| [MyAccount API password update and 2FA support is EA in Preview](#myaccount-api-password-update-and-2fa-support-is-ea-in-preview) | May 24, 2023 |
1414
| [AMR Claims Mapping for IdPs is EA in Preview](#amr-claims-mapping-for-idps-is-ea-in-preview) | May 24, 2023 |
15-
| [Bugs fixed in 2023.05.2](#bugs-fixed-in-2023-05-2) | May 24, 2023 |
15+
| [Bug fixed in 2023.05.2](#bug-fixed-in-2023-05-2) | May 24, 2023 |
1616

1717
#### MyAccount API password update and 2FA support is EA in Preview
1818

@@ -22,11 +22,9 @@ You can now use the [MyAccount API](https://developer.okta.com/docs/api/openapi/
2222

2323
This feature allows admins to configure their org to accept Authentication Method Reference (AMR) claims from SAML or OpenID Connect IdPs during SSO. Mapping AMR claims for third-party IdPs eliminates duplicate factor challenges during user authentication. AMR claims provide important context to Okta during policy evaluation, enabling a better understanding of which factors were used by the external IdP to verify the user's identity. This creates a more seamless and secure user experience, reducing friction, and boosting productivity. See [Add an external Identity Provider](/docs/guides/add-an-external-idp/oktatookta/main/#create-an-identity-provider-in-okta). <!-- OKTA-612157 FF: IDP_AMR_CLAIMS_MAPPING -->
2424

25-
#### Bugs fixed in 2023.05.2
25+
#### Bug fixed in 2023.05.2
2626

27-
* During the Authorization Code flow, claims appeared in the ID token when `alwaysIncludeInToken` was set to `false`. (OKTA-599051)
28-
29-
* Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
27+
Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
3028

3129
### Weekly release 2023.05.1
3230

packages/@okta/vuepress-site/docs/release-notes/2023/index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,11 @@ title: Okta API Products release notes 2023
88

99
| Change | Expected in Preview Orgs |
1010
| ------ | ------------------------ |
11-
| [Bugs fixed in 2023.05.2](#bugs-fixed-in-2023-05-2) | May 24, 2023 |
11+
| [Bug fixed in 2023.05.2](#bug-fixed-in-2023-05-2) | May 24, 2023 |
1212

13-
#### Bugs fixed in 2023.05.2
13+
#### Bug fixed in 2023.05.2
1414

15-
* During the Authorization Code flow, claims appeared in the ID token when `alwaysIncludeInToken` was set to `false`. (OKTA-599051)
16-
17-
* Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
15+
Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
1816

1917
### Weekly release 2023.05.1
2018

0 commit comments

Comments
 (0)