-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Added functionality for Palo Alto Firewall deployments (PANOS) #4575
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added ability to save and reuse API key rather than regenerating a new key on every deployment.
@Neilpang - can you pls merge this into the dev branch? |
fix the ci errors first |
@Neilpang - Made the changes. |
…dded ability to use user/pass OR key
@Neilpang - Can you please run the checks on the latest code? I believe the latest code should pass the CI checks. Thank you. |
@Neilpang - Hi Neil - any updates on the pull request? There have been a few people looking for wildcard cert functionality on PanOS. Right now wildcard cert deployments fail with PANOS without any clear explanation as to the reason (it's the '*' in the filename). Let me know if there are any additional questions you have on the code. Thanks! |
@Neilpang - Checking in to see if you've had a chance to review the PR. Any thoughts / comments? |
@Neilpang - Can you please merge these to the dev branch? |
This resolves #4309 (wildcard certs) as well as issues deploying ecc certificates to Palo Alto firewalls. Wildcard certificates will now have their asterisk
*
replaced withWILDCARD_
on the firewall.Ex: The certificate
*.mydomain.com
will be saved asWILDCARD_.mydomain.com
on PanOS.