<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
0D54z00008FmePhCAJOkta Classic EngineAPI Access ManagementAnswered2022-10-21T13:35:33.000Z2022-10-19T18:33:31.000Z2022-10-21T13:35:33.000Z
Okta Authenticators API - Okta Verify Postman response. When will the compliance change to "required" for Okta Verify?

When will the below-mentioned property change to "Required" when reading the Okta Verify Authenticator from the "api/v1/authenticators" API end point?

Please refer the below image:

 

/help/servlet/rtaImage?refid=0EM4z000005HLPk


  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @Sagar JadavR.47802 (Customer)​,

     

    Thank you for posting on the Okta community page!

     

    I have done some tests upon my Okta environment and it seems that in order for the "fips" option to be set to "REQUIRED", an Early Access functionality needs to be enabled on your tenant. In order to enable the feature, you can go to your Admin Dashboard >> Settings >> Features and here you can find the "FIPS Compliance" functionality that you can turn on in order to have the option available for MFA. If the functionality doesn't show up on the page mentioned previously, the best route to pursue would be to get in contact with your Account Executive in order to discuss about this feature.

     

    After the feature is enabled on your environment, you can access your Admin Dashboard >> Security >> Authenticators >> Okta Verify >> Edit and at the bottom you will find the FIPS Compliance section where if the option is set for only certain devices, the "fips" from the API response will be set as "REQUIRED" and not "OPTIONAL".

     

    I hope the above information is useful!

     

    ------------------------------------------------------------------------------------------------------------------------------------------------

    The October issue of the Okta Community is here and packed with tips on certification, how to earn badges, and new releases. Let us help you stay connected.

    Expand Post
    Selected as Best
  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @Sagar JadavR.47802 (Customer)​,

     

    Thank you for posting on the Okta community page!

     

    I have done some tests upon my Okta environment and it seems that in order for the "fips" option to be set to "REQUIRED", an Early Access functionality needs to be enabled on your tenant. In order to enable the feature, you can go to your Admin Dashboard >> Settings >> Features and here you can find the "FIPS Compliance" functionality that you can turn on in order to have the option available for MFA. If the functionality doesn't show up on the page mentioned previously, the best route to pursue would be to get in contact with your Account Executive in order to discuss about this feature.

     

    After the feature is enabled on your environment, you can access your Admin Dashboard >> Security >> Authenticators >> Okta Verify >> Edit and at the bottom you will find the FIPS Compliance section where if the option is set for only certain devices, the "fips" from the API response will be set as "REQUIRED" and not "OPTIONAL".

     

    I hope the above information is useful!

     

    ------------------------------------------------------------------------------------------------------------------------------------------------

    The October issue of the Okta Community is here and packed with tips on certification, how to earn badges, and new releases. Let us help you stay connected.

    Expand Post
    Selected as Best
This question is closed.
Loading
Okta Authenticators API - Okta Verify Postman response. When will the compliance change to "required" for Okta Verify?