Skip to content

[typescript-axios] Add detection for AWS IAM from schema #21356

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.

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

NiltiakSivad
Copy link

@NiltiakSivad NiltiakSivad commented May 30, 2025

Previous Efforts

Here is the open issue.

I've taken over the effort that was originally started, here. It was suggested in this PR that rather than use a CLI flag like useAwsIamAuth, that we detect IAM Auth from the schema itself.

Summary

This is the first PR of 2. I thought it would be good to talk about the IAM auth detection mechanism before talking about the implementation method in the templates.

At a high-level I'm proposing 3 patterns for detecting AWS IAM Auth.

  1. Check for AWS-specific extension
  2. Check for common AWS V4 signature scheme names
  3. Check for AWS API Gateway URL patterns in servers

It is up for discussion the pro/cons of each, and perhaps we end up with only 1 or a subset of the 3.

Deployment

This is a non-breaking change, as it is adding a variable to be returned to the templates, so I think merging into master is sufficient, but let me know if you think differently! I really hate Java and first PR contributing to this repo so looking for any and all feedback to follow standards/conventions. Any deviation from standards/conventions is not intentional so please lmk.

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @topce (2018/10) @akehir (2019/07) @petejohansonxo (2019/11) @amakhrov (2020/02) @davidgamero (2022/03) @mkusaka (2022/04) @joscha (2024/10)

templateDir: modules/openapi-generator/src/main/resources/typescript-axios
additionalProperties:
npmVersion: 1.0.0
npmName: '@openapitools/typescript-axios-with-aws-iam'
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is my setup, but let me know if you think I should add a specific combination

@@ -26,7 +26,9 @@
"prepare": "npm run build"
},
"dependencies": {
"axios": "{{axiosVersion}}"
"axios": "{{axiosVersion}}"{{#withAWSV4Signature}},
Copy link
Author

@NiltiakSivad NiltiakSivad May 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can remove this before merge but wanted to show it working with a conditional

@NiltiakSivad NiltiakSivad force-pushed the typescript-axios-detect-iam-auth branch from 621588e to f9c7ce4 Compare May 30, 2025 19:12
version: 1.0.0
description: Test API for AWS IAM authentication detection
servers:
- url: https://abc123.execute-api.us-east-1.amazonaws.com/prod
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pattern 3

type: apiKey
name: Authorization
in: header
x-amazon-apigateway-authtype: awsSigv4
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pattern 1

@@ -30,7 +30,7 @@ public class CodegenSecurity {
// Those are to differentiate basic and bearer authentication
// isHttpSignature is to support HTTP signature authorization scheme.
// https://datatracker.ietf.org/doc/draft-cavage-http-signatures/
public Boolean isBasicBasic, isBasicBearer, isHttpSignature;
public Boolean isBasicBasic, isBasicBearer, isHttpSignature, isAWSV4Signature;
Copy link
Author

@NiltiakSivad NiltiakSivad May 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surprised this wasn't already here given AWS IAM is supported in the go generator? Anticipating some feedback 👂

servers:
- url: https://abc123.execute-api.us-east-1.amazonaws.com/prod
security:
- iam: []
Copy link
Author

@NiltiakSivad NiltiakSivad May 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pattern 2, which reflects on line 64, 16, 30, 51

@NiltiakSivad NiltiakSivad changed the title [typescript-axios] Add detection for AWS IAM [typescript-axios] Add detection for AWS IAM from schema May 30, 2025
const localVarQueryParameter = {} as any;

// authentication iam required
await setApiKeyToObject(localVarHeaderParameter, "Authorization", configuration)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the next PR this would be replaced with something that returns the signed AWS headers

@OpenAPITools OpenAPITools deleted a comment from wisecode1 May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant