<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
0D5WR00002GDjWo0ALOkta Classic EngineAuthenticationAnswered2026-10-30T18:14:56.000Z2026-10-12T06:32:22.000Z2026-10-30T18:14:56.000Z

saik.23639 (Customer) asked a question.

Invalid grant

{

    "error": "invalid_grant",

    "error_description": "The NHI Authentication Tokens SKU is not enabled. Contact your Account Executive to enable the SKU to use the requested grant type or token exchange flow."

} getting this error when i am trying to retrieve access token. can anyone help me through it?

 


  • Mihai N. (Okta, Inc.)

    Hi @saik.23639 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    You are receiving an invalid_grant error with the description "The NHI Authentication Tokens SKU is not enabled" when requesting an access token from Okta, and you are asking how to resolve it.

    Root Cause: The Okta org does not have the licensed SKU that is required for the grant type or token exchange flow in your request. The error is returned by the authorization server because the entitlement is missing, so changing the request parameters will not resolve it.

     

    Solution: Confirm the entitlement with your Okta account team, then retry the request once the SKU is active.

    1. Verify the grant type in your request. Confirm that the value you send, such as token exchange, is the grant type named in the error context and that you are calling the authorization server endpoint for your org.
    2. Check your org's licensing. Ask your Okta Account Executive whether the NHI Authentication Tokens SKU is included in your contract. Okta enables this SKU for the org, so an administrator cannot turn it on from the Admin Console.
    3. Request the SKU enablement from your Account Executive if it is not included. Provide your org domain and the grant type you need.
    4. Retry the token request after the SKU is enabled. Use the same client credentials and parameters, and confirm that the response returns an access_token.
    5. Post technical implementation questions to the Okta Developer Forum at devforum.okta.com if the error persists after the SKU is confirmed, since that forum covers API and grant type implementation in depth.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @saik.23639 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    You are receiving an invalid_grant error with the description "The NHI Authentication Tokens SKU is not enabled" when requesting an access token from Okta, and you are asking how to resolve it.

    Root Cause: The Okta org does not have the licensed SKU that is required for the grant type or token exchange flow in your request. The error is returned by the authorization server because the entitlement is missing, so changing the request parameters will not resolve it.

     

    Solution: Confirm the entitlement with your Okta account team, then retry the request once the SKU is active.

    1. Verify the grant type in your request. Confirm that the value you send, such as token exchange, is the grant type named in the error context and that you are calling the authorization server endpoint for your org.
    2. Check your org's licensing. Ask your Okta Account Executive whether the NHI Authentication Tokens SKU is included in your contract. Okta enables this SKU for the org, so an administrator cannot turn it on from the Admin Console.
    3. Request the SKU enablement from your Account Executive if it is not included. Provide your org domain and the grant type you need.
    4. Retry the token request after the SKU is enabled. Use the same client credentials and parameters, and confirm that the response returns an access_token.
    5. Post technical implementation questions to the Okta Developer Forum at devforum.okta.com if the error persists after the SKU is confirmed, since that forum covers API and grant type implementation in depth.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • saik.23639 (Customer)

    I have created this okta account for testing purpose. who is the account executive and how to contact him?

     

Loading
Invalid grant
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply