Skip to content
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

CAMEL-18099: Adding Azure Identity authentication support #7615

Merged
merged 8 commits into from May 18, 2022

Conversation

yuhusolutions
Copy link
Contributor

Hi there, this PR add supports for Azure Identity authentication for the AzureBlob component.
It changes the default behavior from "shared key" (discouraged) to AzureIdentity authentication.

Added deps to the pom.xml for azure-identity, and refactored the boiler plate code to support other types of token auth if need be for the future (e.g. SAS token). From now on, the authentication type needs to be specified to switch from default.

Tested existing and new ways to authenticate, with the existing test and using a consumer & producer route.
Could not find regression.

Note that I updated the doc accordingly, part of it seems to be generated.

Let me know your comments.

Thanks.

  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue CAMEL-18099.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
    Below are the contribution guidelines:
    https://github.com/apache/camel/blob/main/CONTRIBUTING.md

@github-actions
Copy link
Contributor

⚠️ This PR changes Camel components and will be tested automatically.

@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 1 component(s) tested

…eBlob component.

- organized imports for checkstyle import order.
Copy link
Contributor

@oscerd oscerd left a comment

Choose a reason for hiding this comment

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

Just minor findings, looks good overall. I think it should be nice to add some examples of configuration in the src/main/docs/*.adoc file for this component. Also I do think we should do the same for all the Azure components we have. Thanks a lot for this PR.

Copy link
Contributor

@davsclaus davsclaus left a comment

Choose a reason for hiding this comment

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

LGTM however the enums should be changed style as @oscerd also mentioned

@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 1 component(s) tested

Hugo Veillette added 4 commits May 16, 2022 15:41
PR Review, fixing * imports to fully qualified.
PR Review, Java convention for Enums (missed ref in doc)
@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 1 component(s) tested

@oscerd
Copy link
Contributor

oscerd commented May 17, 2022

@yuhusolutions can you please check the tests?

- Ran mvm formatter:format
- Fixed tests to specify CredentialType
- Fixed regression in clientFactory
@github-actions
Copy link
Contributor

✔️ Finished component verification: 0 component(s) test failed out of 1 component(s) tested

@davsclaus davsclaus merged commit c7f41de into apache:main May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants