04-30-2021 07:06 AM
We have found instances where applications were changed in house to use a different port than the default. So we are in discussion as to what is the best approach to create policy rules.
Below are the two policy rules involving AppID is what we believe to best address our situation:
1. appID with Service set to protocol port that the app is set to use
2. appID with Service set no protocol port
We were wanting to just create one policy rule but realize we may have to settle for multiple.
I have been unable to find documentation that discusses the best approach involving the above and just needed to discuss the pros and cons.
05-03-2021 11:45 AM
In these instances I would just create a security rulebase entry with the app-id and a service-object set for the protocol and port you have modified it to. This would be a standalone entry; don't try to combine standard app-id traffic and what you have to customize.
05-01-2021 02:21 AM - edited 05-01-2021 07:59 AM
Reasons to use the service. App ID helps developers to easily add authentication to their web and mobile apps with few lines of code
05-03-2021 11:45 AM
In these instances I would just create a security rulebase entry with the app-id and a service-object set for the protocol and port you have modified it to. This would be a standalone entry; don't try to combine standard app-id traffic and what you have to customize.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
