<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Using 'q' Parameter in Okta's Policy API Does Not Return Desired Results
API Access Management
Okta Classic Engine
Overview

When an end user uses Okta's Policy API to make a GET API call to list policies by type, the "q" parameter is used to refine the query by policy name.

However, when using the "q" parameter, the API call will return all policies instead of filtering the list by policy name. 

  • For example, an API call is made to the Policy endpoint GET https://<domain>.okta.com/api/v1/policies?type=PASSWORD&q=TEST. This will return all the Password policies for the Okta tenant.

The expectation is that the "q" parameter should be honoured in the query, and only Password policies with names starting with TEST should be returned. 

Policy endpoint

This is an issue seen in Okta Classic with Policy types - "OKTA_SIGN_ON" or "PASSWORD" or "MFA_ENROLL"

Applies To
  • Okta Classic Engine
Cause

This is a known limitation in Okta Classic.

Solution

The issue is resolved by enabling an internal Feature Flag. Please contact Okta Support to enable this flag. 

Loading
Using 'q' Parameter in Okta's Policy API Does Not Return Desired Results