<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
0D54z00007avFKfCAMOkta Classic EngineAPI Access ManagementAnswered2022-04-22T20:25:31.000Z2022-04-22T14:57:06.000Z2022-04-22T20:25:31.000Z

BrandonE.18266 (Customer) asked a question.

What Components do I need to connect Okta with an AWS API Gateway? Do I need to pay extra for a custom authorization server?

I have a Serverless Application behind an AWS lambda that I would like to deploy behind an AWS API gateway with a custom authorizer that uses Okta.

 

I was trying to follow the documentation from this site: https://www.oktaapicenter.com/

 

However, it mentions a "custom API server" that I find missing from my account. Is this an extra paid feature? Or is this just a default feature I don't have enabled?


  • BrandonE.18266 (Customer)

    So does this task require a custom authorization server or not? Do I need to buy the "API Access Management" feature to have this capability or not?

     

    The documentation states that there's a "Default org authorization server" at https://YOUR-ORG-DOMAIN (clearly separating this from the custom authorization server) (not to be confused with the "default" custom authorization server), but makes no distinction on whether that's a paid as well. Is this paid? Does this work in lieu of the "custom authorization server" -- and if not, why?

    Expand Post
This question is closed.
Loading
What Components do I need to connect Okta with an AWS API Gateway? Do I need to pay extra for a custom authorization server?