-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add Destination/Source Ports literals to Access Rules #96
Comments
You are welcome! Though, I must admit I didn't write that particular bit of the code. Someone in the community did. :-) |
Yeah, I think is more a feature request than an ''Issue" . Would it be possible to put this request out there, in case someone can help with this. |
I'm glad I asked. I mis-read your message and didn't see any request in it. (I know. I've re-read it and it is obvious. I just missed the message's meaning last time.) |
Alas, the online API documentation doesn't explicitly describe whether "literal" is a valid input for AccessRules. I'll have to spin up an FMC and check it from there. |
I tried to mess around with the API and was able to create Access rules with literal ports. Here is a sample Payload.
|
Hello Guys,
First of all, thanks for this
It will be really great to have the ability to add port literals for Access Rules just like we can with source and destination networks. Having to create port objects for access rules has left us with a lot of duplicated port objects.
Thanks.
The text was updated successfully, but these errors were encountered: