Skip to content

OAMP - remove device probe mentions #5370

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.

Sign up for GitHub

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
brentschaus-okta merged 2 commits into from
Mar 24, 2025
Merged

OAMP - remove device probe mentions #5370

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0919ca3
removes offending content
brentschaus-okta Mar 20, 2025
2d34b2c
wut
brentschaus-okta Mar 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/@okta/vuepress-site/docs/concepts/policies/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ Use the [Authentication Policies page](https://help.okta.com/okta_help.htm?type=

#### Device assurance policies

Use [device assurance policies](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/DeviceAssurance/) to check sets of security-related device attributes. Device assurance works as part of your [authentication policies](#authentication-policies).
Use [device assurance policies](/docs/guides/device-assurance-policies/main/) to check sets of security-related device attributes. Device assurance works as part of your [authentication policies](#authentication-policies).

For example, you can configure a device assurance policy to check whether a specific operating system version is installed on a device. Once verified, that device can be used to access Okta-protected resources.

Expand Down
9 changes: 2 additions & 7 deletions ...es/@okta/vuepress-site/docs/guides/okta-account-management-policy/main/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ Add this rule to your Okta account management policy if your org doesn't already

If your org already uses phishing-resistant authenticators, see [Add a rule for authenticator enrollment](#add-a-rule-for-authenticator-enrollment).

> **Note:** This rule relies on [managed devices](https://support.okta.com/help/s/article/Howto-Get-a-List-of-All-Managed-and-NotManaged-Devices-in-Okta?language=en_US) and [IP Network Zones](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).
> **Note:** This rule relies on [IP Network Zones](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).

If you want to add this rule using the Admin Console, see [Add a rule for your first phishing-resistant authenticator](https://help.okta.com/okta_help.htm?type=oie&id=ext-oamp-enroll-first).

Expand All @@ -134,7 +134,6 @@ Send a POST request to the `/api/v1/policies/{policyId}/rules` endpoint. Conside
* Use the value of `id` from the [GET call](#retrieve-the-okta-account-management-policy-id) as the value of `policyId` in your request.
* Set the value of `priority` to `1`.
* Set values for `network.connection` and `network.include`.
* Set the value of `device.managed` to `true`.

```bash
curl --location --globoff 'https://{yourOktaDomain}/api/v1/policies/{policyId/rules?activate=true' \
Expand Down Expand Up @@ -171,10 +170,6 @@ curl --location --globoff 'https://{yourOktaDomain}/api/v1/policies/{policyId/ru
"exclude": []
}
},
"device": {
"registered": true,
"managed": true
},
"riskScore": {
"level": "LOW"
},
Expand Down Expand Up @@ -228,7 +223,7 @@ curl --location --globoff 'https://{yourOktaDomain}/api/v1/policies/{policyId/ru

### User experience

Users must be on a managed device, inside a trusted network zone, and demonstrate low risk behavior before they enroll the designated phishing-resistant authenticator. If they don't meet these requirements, all fields in their profile settings are read-only, including the Reset, Update, and Remove options for their existing security methods. The phishing-resistant authenticators that they haven't enrolled are hidden, which means that they can't access any apps with phishing-resistant authentication policies.
Users must be inside a trusted network zone and demonstrate low risk behavior before they enroll the designated phishing-resistant authenticator. If they don't meet these requirements, all fields in their profile settings are read-only, including the Reset, Update, and Remove options for their existing security methods. The phishing-resistant authenticators that they haven't enrolled are hidden, which means that they can't access any apps with phishing-resistant authentication policies.

This rule also applies to authenticator unenrollment, and users can lock themselves out if they unenroll too many authenticators. Encourage users to always maintain one phishing-resistant authenticator.

Expand Down
2 changes: 1 addition & 1 deletion yarn.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10243,7 +10243,7 @@ [email protected]:

qs@~6.5.2:
version "6.5.3"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.5.3.tgz#3aeeffc91967ef6e35c0e488ef46fb296ab76aad"
resolved "https://artifactory.es.atko.services/artifactory/api/npm/npm-okta-master/qs/-/qs-6.5.3.tgz#3aeeffc91967ef6e35c0e488ef46fb296ab76aad"
integrity sha512-qxXIEh4pCGfHICj1mAJQ2/2XVZkjCDTcEgfoSQxc/fYivUZxTkk7L3bDBJSoNrEzXI17oUO5Dp07ktqE5KzczA==

query-string@^7.1.3:
Expand Down