-
Notifications
You must be signed in to change notification settings - Fork 651
OKTA-1044206 - add rss icons #5887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
annejuan-okta
merged 8 commits into
release-2026.01.0
from
bd-okta-1044206-add-rss-icons
Jan 7, 2026
Merged
Changes from 6 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
488883d
First pass with adding new 2026 folders and updating archive information
annejuan-okta d263252
Updated wording in navbar
annejuan-okta 4899d14
Added RN entries
annejuan-okta 5d2df28
Missing date
annejuan-okta 7262ee8
Added icon and references in release notes files
brianduffield-okta e49b1bf
Minor formating updates as per local review; add 2025 links for ag an…
brianduffield-okta ecb0e88
fix incorrect feed
brianduffield-okta 51461ba
Merge branch 'release-2026.01.0' into bd-okta-1044206-add-rss-icons
annejuan-okta File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
18 changes: 18 additions & 0 deletions
18
packages/@okta/vuepress-site/.vuepress/public/img/icons/Feed-icon.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
15 changes: 15 additions & 0 deletions
15
packages/@okta/vuepress-site/docs/release-notes/2026-okta-access-gateway/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| --- | ||
| title: Okta Access Gateway API release notes 2026 | ||
|
|
||
| --- | ||
|
|
||
| # Okta Access Gateway API release notes (2026) | ||
|
|
||
| <a href="/rss/access-gateway.xml"> | ||
| <img src="/img/icons/Feed-icon.svg" alt="RSS" width="20" height="20" /> | ||
| Subscribe to RSS | ||
| </a><br><br> | ||
|
|
||
| Access Gateway is available for both Okta Classic and Identity Engine. | ||
|
|
||
| [Okta Access Gateway API release notes (2025)](/docs/release-notes/2025-okta-access-gateway/) |
18 changes: 18 additions & 0 deletions
18
packages/@okta/vuepress-site/docs/release-notes/2026-okta-aerial/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| title: Okta Aerial API release notes 2026 | ||
| --- | ||
|
|
||
| # Okta Aerial API release notes (2026) | ||
|
|
||
| <a href="/rss/aerial.xml"> | ||
| <img src="/img/icons/Feed-icon.svg" alt="RSS" width="20" height="20" /> | ||
| Subscribe to RSS | ||
| </a><br><br> | ||
|
|
||
| These release notes list customer-visible changes to the Okta Aerial API. Okta Aerial aligns with the Okta Classic Engine and Okta Identity Engine release, but updates to the Aerial service deploy from outside their release dates. | ||
|
|
||
| * The Aerial services preview date are expected updates to the preview environment (`https://aerial-sandbox.okta.com`). | ||
|
|
||
| * The Aerial services production date are expected updates to the production environment (`https://aerial-apac.okta.com`). | ||
|
|
||
| See also [Introduction to the Okta Aerial API](https://developer.okta.com/docs/api/openapi/aerial/guides/overview/). |
103 changes: 103 additions & 0 deletions
103
packages/@okta/vuepress-site/docs/release-notes/2026-okta-identity-engine/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,103 @@ | ||
| --- | ||
| title: Okta Identity Engine API release notes 2026 | ||
| --- | ||
|
|
||
| <ApiLifecycle access="ie" /> | ||
|
|
||
| # Okta Identity Engine API release notes (2026) | ||
|
|
||
| <a href="/rss/identity-governance.xml"> | ||
| <img src="/img/icons/Feed-icon.svg" alt="RSS" width="20" height="20" /> | ||
| Subscribe to RSS | ||
| </a> | ||
|
|
||
| ## January | ||
|
|
||
| ### Monthly release 2026.01.0 | ||
| <!-- Published on: 2026-01-08T12:00:00Z --> | ||
|
|
||
| | Change | Expected in Preview Orgs | | ||
| |--------|--------------------------| | ||
| | [Bring your own telephony credentials is EA](#bring-your-own-telephony-credentials-is-ea) | January 7, 2026 | | ||
| | [Client update policy is EA in Preview](#client-update-policy-is-ea-in-preview) | January 7, 2026 | | ||
| | [Encryption of ID tokens and access tokens is GA in Production](#encryption-of-id-tokens-and-access-tokens-is-ga-in-production) | August 7, 2025 | | ||
| | [Unified claims generation for custom apps is GA in Production](#unified-claims-generation-for-custom-apps-is-ga-in-production) | July 30, 2025 | | ||
| | [Custom FIDO2 AAGUID is GA in Preview](#custom-fido2-aaguid-is-ga-in-preview) | January 7, 2026 | | ||
| | [Improvements to the global session policy MFA requirements is GA in Production](#improvements-to-the-global-session-policy-mfa-requirements-is-ga-in-production) | December 10, 2025 | | ||
| | [Additional Anything-as-a-Source API endpoints is GA in Production](#additional-anything-as-a-source-api-endpoints--is-ga-in-production) | December 10, 2025 | | ||
| | [Anything-as-a-Source for groups and group memberships API is GA in Production](#anything-as-a-source-for-groups-and-group-memberships-api-is-ga-in-production) | December 10, 2025 | | ||
| | [Okta account management policy protection for password expiry flows is GA in Production](#okta-account-management-policy-protection-for-password-expiry-flows-is-ga-in-production) | July 2, 2025 | | ||
| | [New password complexity property is GA in Preview](#new-password-complexity-property-is-ga-in-preview) | June 4, 2025 | | ||
| | [Developer documentation updates in 2026.01.0](#developer-documentation-updates-in-2026-01-0) | January 7, 2026 | | ||
| | [Bugs fixed in 2026.01.0](#bugs-fixed-in-2026-01-0)| January 7, 2026 | | ||
|
|
||
| #### Bring your own telephony credentials is EA | ||
|
|
||
| You can now connect your own telephony provider using a new simplified setup that doesn’t require you to use a telephony inline hook. You can handle usage billing directly with your provider. Okta currently supports Twilio and Telesign. | ||
|
|
||
| To configure your own telephony credentials, you can use the [Custom Telephony Provider API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/CustomTelephonyProvider/) or you can use the [Admin Console](https://help.okta.com/okta_help.htm?type=oie&id=configure-telephony-providers). | ||
| <!-- OKTA-1075267 CUSTOM_TELEPHONY_PROVIDERS--> | ||
|
|
||
| #### Client update policy is EA in Preview | ||
|
|
||
| The Policies API now supports the `CLIENT_POLICY` type, enabling you to enforce or defer app updates across different device platforms. This lets you programmatically align app versions with internal change management processes. See the [Policies API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/listPolicies) and [Release controls policy](https://help.okta.com/okta_help.htm?type=oie&id=ext-ov-release-controls). <!-- OKTA_VERIFY_RELEASE_CONTROL_POLICY OKTA-1036332 January 7, 2026 --> | ||
|
|
||
| #### Encryption of ID tokens and access tokens is GA in Production | ||
|
|
||
| You can now encrypt OIDC ID tokens for Okta-protected custom app integrations using JSON Web Encryption. You can also now encrypt access tokens minted by a custom authorization server. See [Key management](/docs/guides/key-management/main/). <!-- OIDC_TOKEN_ENCRYPTION OKTA-978457 --> | ||
|
|
||
| #### Unified claims generation for custom apps is GA in Production | ||
|
|
||
| Unified claims generation is a new streamlined interface for managing claims (OIDC) and attribute statements (SAML) for Okta-protected custom app integrations. In addition to group and user profile claims, the following new claim types are available: `entitlements` (required OIG), `device.profile`, `session.id`, and `session.amr`. See [Okta Expression Language in Identity Engine](/docs/reference/okta-expression-language-in-identity-engine/). | ||
|
|
||
| <!-- GENERIC_FEDERATED_CLAIM_LAYER OKTA-971830 --> | ||
|
|
||
| #### Custom FIDO2 AAGUID is GA in Preview | ||
|
|
||
| You can now use the [Authenticators API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Authenticator/) to create, view, and update custom Authenticator Attestation Global Unique Identifiers (AAGUIDs). | ||
|
|
||
| Admins can add non-FIDO Metadata Service (MDS) security keys and other authenticators and have more granular control over them. This extends FIDO2 (WebAuthn) authenticator support to a wider range of security keys and other authenticators, which gives admins greater flexibility and control over the security in their environment. | ||
|
|
||
| #### Improvements to the global session policy MFA requirements is GA in Production | ||
|
|
||
| The Policy API now correctly enforces MFA requirements for every sign-in when **New Device** is included as a behavior and MFA is required in a global session policy. See the [Policy API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/createPolicyRule!path=3/actions/signon/factorPromptMode&t=request). | ||
|
|
||
| <!-- OKTA-1070041 DISALLOW_INVALID_BEHAVIOR_AND_FACTOR_MODE_COMBINATION_FOR_GSP, preview date: Dec 10, 2025 --> | ||
|
|
||
| #### Additional Anything-as-a-Source API endpoints is GA in Production | ||
|
|
||
| Anything-as-a-Source (XaaS) capabilities allow customers to use a custom identity source with Okta. With XaaS, customers can source entities such as users into Okta's Universal Directory by connecting a custom HR app or a custom database. This release offers Anything-as-a-Source APIs for both individual operations and bulk operations on groups, group memberships, and users. Okta now enables creating and updating users, creating and updating groups, and managing group memberships into Okta’s Universal Directory from any identity source using the Identity Source APIs. See [Identity Sources](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentitySource/). | ||
|
|
||
| <!-- OKTA-1063549 IDENTITY_SOURCE_MANAGE_INDIVIDUAL_ENTITIES --> | ||
|
|
||
| #### Anything-as-a-Source for groups and group memberships API is GA in Production | ||
|
|
||
| Anything-as-a-Source (XaaS) capabilities allow customers to use a custom identity source with Okta. With XaaS, customers can source entities such as users into Okta's Universal Directory by connecting a custom HR app or a custom database. This release offers XaaS capabilities with groups and group memberships, allowing customers to start sourcing groups with XaaS. Okta now enables creating and updating users, creating and updating groups, and managing group memberships into Okta’s Universal Directory from any identity source using the Identity Source APIs. See [Identity Sources](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentitySource/). | ||
|
|
||
| <!-- IDENTITY_SOURCE_APPS_GROUPS OKTA-1009858 --> | ||
|
|
||
| #### Okta account management policy protection for password expiry flows is GA in Production | ||
|
|
||
| This feature improves the security posture of customer orgs by protecting the password expiry flow with the Okta account management policy. Password expiry flows now require the assurance defined in an org's Okta account management policy. | ||
|
|
||
| You can now use the [`metadata`](/docs/reference/okta-expression-language-in-identity-engine/#okta-account-management) component in an Expression Language condition for an Okta account management policy. You can only use `metadata` in an expression that’s related to password expiry. See [Enable password expiry](https://help.okta.com/okta_help.htm?type=oie&id=oamp-enable-password-expiry) | ||
|
|
||
| <!-- OKTA-853468 AMP_FOR_PASSWORD_EXPIRY preview org: july 2, 2025 --> | ||
|
|
||
| #### New password complexity property is GA in Preview | ||
|
|
||
| You can now use the `oelStatement` property to block words from being used in passwords. This feature enhances security by allowing you to customize your password strength requirements. See the [Policy API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/createPolicy!path=3/settings/password/complexity/oelStatement&t=request). | ||
|
|
||
| <!-- OKTA-849300 PASSWORD_POLICY_OEL_STATEMENT Preview date: June 4, 2025--> | ||
|
|
||
| #### Developer documentation updates in 2026.01.0 | ||
|
|
||
| * The new [Express Configuration customer configuration guide template](/docs/guides/express-config-guide-template/main/) is available to help Express Configuration partners create accurate configuration guides for their customers. This resource provides standardized instructions for setting up apps that use Express Configuration, covering functionalities such as SSO, Universal Logout, and SCIM provisioning. | ||
| * The rate limits documentation has now been revised and updated on the References tab. New updates include detailed explanations on rate limit buckets, as well as more information on how to increase your rate limits. See the [Rate Limits overview](/docs/reference/rate-limits/). | ||
| * The Okta API release notes now provide an RSS feed for each API release note category: [Classic Engine](/docs/release-notes/2026/), [Identity Engine](/docs/release-notes/2026-okta-identity-engine/), [Identity Governance](/docs/release-notes/2026-okta-identity-governance/), [Privileged Access](/docs/release-notes/2026-okta-privileged-access/), [Access Gateway](/docs/release-notes/2026-okta-access-gateway/), and [Aerial](/docs/release-notes/2026-okta-aerial/). Click the RSS icon to subscribe. | ||
|
|
||
| #### Bugs fixed in 2026.01.0 | ||
|
|
||
| * The following attributes weren't properly being gated as reserved attributes: `orgid`, `activationstatus`, `apistatus`, `logintype`, `initialreconcilecomplete`, `activationdate`, `statuschangeddate`, `apilastupdate`, `passwordexpirationguess`, `passwordexpirationcursor`, `numunlocks`, `changedstatus`. See [Review reserved attributes](https://help.okta.com/okta_help.htm?type=oie&id=reserved-attributes). (OKTA-1049339) | ||
|
|
||
| * An error sometimes occurred when an admin attempted to update the username for an app user. (OKTA-1047716) | ||
62 changes: 62 additions & 0 deletions
62
...s/@okta/vuepress-site/docs/release-notes/2026-okta-identity-governance/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| --- | ||
| title: Okta Identity Governance API release notes 2026 | ||
| --- | ||
|
|
||
| # Okta Identity Governance API release notes (2026) | ||
|
|
||
| <a href="/rss/identity-governance.xml"> | ||
| <img src="/img/icons/Feed-icon.svg" alt="RSS" width="20" height="20" /> | ||
| Subscribe to RSS | ||
| </a><br><br> | ||
|
|
||
| Okta Identity Governance is available for both Okta Classic and Identity Engine. | ||
|
|
||
| ## January | ||
|
|
||
| ### Monthly release 2026.01.0 | ||
| <!-- Published on: 2026-01-08T12:00:00Z --> | ||
|
|
||
| | Change | Expected in Preview Orgs | | ||
| |--------|--------------------------| | ||
| | [Security access reviews API is GA in Production](#security-access-reviews-api-is-ga-in-production) | September 10, 2025 | | ||
| | [Permalink ID in V1 access request is Beta](#permalink-id-in-v1-access-request-is-beta) | January 8, 2026 | | ||
| | [AD group support in Access Requests is GA in Production](#ad-group-support-in-access-requests-is-ga-in-production) | December 10, 2025 | | ||
| | [My Access Certification Reviews API is Beta](#my-access-certification-reviews-api-is-beta) | January 8, 2026 | | ||
| | [Developer documentation updates in 2026.01.0](#developer-documentation-updates-in-2026-01-0) | January 7, 2026 | | ||
|
|
||
| #### Security access reviews API is GA in Production | ||
|
|
||
| Security access reviews are a new, security-focused type of access review that can be automatically triggered by events. These reviews provide a unified view of a user's access and contextual information about their access history. Also included is an AI-generated access summary, allowing you to investigate and take immediate remediation act | ||
|
|
||
| ions like revoking access. See [Security Access Reviews](https://help.okta.com/okta_help.htm?type=oie&id=csh-sar) in the product documentation. | ||
|
|
||
| See the [Security Access Reviews](https://developer.okta.com/docs/api/iga/openapi/governance.api/tag/Security-Access-Reviews/) API and [Launch a security access review](/docs/guides/iga-security-access-review/main/) guide for details on how to trigger security access reviews through the API. | ||
|
|
||
| <!-- OKTA-1002587 IGA_SECURITY_ACCESS_REVIEW Preview date: Sept 10, 2025 --> | ||
|
|
||
| #### Permalink ID in V1 access request is Beta | ||
|
|
||
| <ApiLifecycle access="beta" /> | ||
|
|
||
| A new `permalinkId` property is returned in [V1 access request](https://developer.okta.com/docs/api/iga/openapi/governance.requests.admin.v1/tag/Requests/) responses. This property is a user-friendly, immutable identifier that resolves to the request. Users can use this identifier (in the form of a permalink) to navigate back to the request on the web page. See [`permalinkId`](https://developer.okta.com/docs/api/iga/openapi/governance.requests.admin.v1/tag/Requests/#tag/Requests/operation/getRequest!c=200&path=0/permalinkId&t=response). | ||
| <!-- OKTA-1060094 Preview date: Jan 8, 2026 --> | ||
|
|
||
| #### AD group support in Access Requests is GA in Production | ||
|
|
||
| Users can now request access to Active Directory (AD)-sourced groups directly within Access Requests. This enhancement enables seamless governance and automatically fulfills and revokes (if time-bound) access in AD, strengthening your security posture and eliminating the need for duplicate groups or custom Workflows. | ||
|
|
||
| You must have [Bidirectional Group Management with Active Directory](https://help.okta.com/okta_help.htm?type=oie&id=ad-bidirectional-group-mgmt) configured in your org to have governance AD group support. See [Access governance for AD groups](https://help.okta.com/okta_help.htm?type=oie&id=ad-bidirectional-group-mgt-configure). | ||
|
|
||
| For users to request access to AD groups, admins must first create a request condition with an AD-sourced group access scope. Use the [Create a request condition](https://developer.okta.com/docs/api/iga/openapi/governance.requests.admin.v2/tag/Request-Conditions/#tag/Request-Conditions/operation/createResourceRequestConditionV2) request and set `accessScopeSettings.type` to `GROUP`. In the `accessScopeSettings.group` list, specify your AD-sourced group IDs that are requestable. | ||
| <!-- OKTA-1059727, OKTA-1036354 ACCESS_REQUEST_AD_GROUPS Preview date: Dec 10, 2025 --> | ||
|
|
||
| #### My Access Certification Reviews API is Beta | ||
|
|
||
| <ApiLifecycle access="beta" /> | ||
|
|
||
| The [My Access Certification Reviews](https://developer.okta.com/docs/api/iga/openapi/governance.requests.enduser.v2/tag/My-Access-Certification-Reviews/#tag/My-Access-Certification-Reviews) API enables end users to retrieve reviews and associated details assigned to them. The responses from this API are specifically for the authenticated user (the end user) making the request. See [List all managed connections for my review](https://developer.okta.com/docs/api/iga/openapi/governance.requests.enduser.v2/tag/My-Access-Certification-Reviews/#tag/My-Access-Certification-Reviews/operation/listMyManagedConnections). | ||
| <!-- OKTA-1057908 Preview date: Jan 8, 2026 --> | ||
|
|
||
| #### Developer documentation updates in 2026.01.0 | ||
|
|
||
| The new [Manage Okta Identity Governance resources using Terraform](/docs/guides/terraform-oig-resources/main/) guide explains how to manage Okta Identity Governance (OIG) resources with Terraform. It details how to create, import, and modify OIG resources using your Terraform configuration. |
14 changes: 14 additions & 0 deletions
14
...ges/@okta/vuepress-site/docs/release-notes/2026-okta-privileged-access/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| title: Okta Privileged Access API release notes 2026 | ||
| --- | ||
|
|
||
| # Okta Privileged Access API release notes (2026) | ||
|
|
||
| <a href="/rss/privileged-access.xml"> | ||
| <img src="/img/icons/Feed-icon.svg" alt="RSS" width="20" height="20" /> | ||
| Subscribe to RSS | ||
| </a><br><br> | ||
|
|
||
| Okta Privileged Access (OPA) is available for both Okta Classic and Identity Engine. | ||
|
|
||
| [Okta Privileged Access API release notes 2025](/docs/release-notes/2025-okta-privileged-access/) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.