Skip to content

Commit

Permalink
remove rn per doc action
Browse files Browse the repository at this point in the history
  • Loading branch information
susanharper-okta committed Jun 1, 2023
1 parent c1e5b2f commit acb6c18
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 10 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ title: Okta Identity Engine API Products release notes 2023
| ------ | ------------------------ |
| [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 |
| [AMR Claims Mapping for IdPs is EA in Preview](#amr-claims-mapping-for-idps-is-ea-in-preview) | May 24, 2023 |
| [Bugs fixed in 2023.05.2](#bugs-fixed-in-2023-05-2) | May 24, 2023 |
| [Bug fixed in 2023.05.2](#bug-fixed-in-2023-05-2) | May 24, 2023 |

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

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

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 -->

#### Bugs fixed in 2023.05.2
#### Bug fixed in 2023.05.2

* During the Authorization Code flow, claims appeared in the ID token when `alwaysIncludeInToken` was set to `false`. (OKTA-599051)

* Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)

### Weekly release 2023.05.1

Expand Down
8 changes: 3 additions & 5 deletions packages/@okta/vuepress-site/docs/release-notes/2023/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,11 @@ title: Okta API Products release notes 2023

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

#### Bugs fixed in 2023.05.2
#### Bug fixed in 2023.05.2

* During the Authorization Code flow, claims appeared in the ID token when `alwaysIncludeInToken` was set to `false`. (OKTA-599051)

* Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)
Token inline hooks failed even when a URL claim name was correctly encoded with a JSON pointer. (OKTA-602794)

### Weekly release 2023.05.1

Expand Down

0 comments on commit acb6c18

Please sign in to comment.