-
Notifications
You must be signed in to change notification settings - Fork 26
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
Possible to use client id / secret? #4
Comments
Maybe something like this would work. |
hey thanks for the suggestion! This will be a future blog post, actually :D stay tuned! |
@alexandramartinez it looks like you compelted this blog post and resolved this issue. Suggestion - I wouldn't include (even a fake) client secret in the blog post. You may want to update it to be blurred or something along those lines. This has been insanely helpful btw - haven't implemented it yet but seems very promising. Thanks! |
@rmcelroy-hylaine A lot of people prefer to see how the credentials look like so they can see they're on the right track. I use free accounts that stop working after 30 days and edit the credentials a bit. But thank you for the suggestion! Security first :D I hope you find it useful :) |
Client ID + Client Secret auth can be found here: https://github.com/alexandramartinez/github-actions/tree/connected-app |
github-actions/.github/workflows/build.yml
Line 84 in aab5dca
As more and more organizations need to move to 2FA in Anypoint platform, there is a recommendation to use "Connected Apps".
How can we change this to utilize that instead?
I see that it should be possible when specifying it in the pom.xml file
https://docs.mulesoft.com/mule-runtime/4.4/deploy-to-cloudhub#cloudhub-deploy-reference
Also on another note, shouldn't it be possible to deploy without the need to specify it on the pom.xml file?
It is strange to specify such things directly in the application it self.
The text was updated successfully, but these errors were encountered: