01-07-2022 12:21 PM
Hi, happy new year!
It used to be the case that profile type was not readily available to use in authorization policies, but that is no longer the case. So what is the current use case for identity groups ? Just a higher order classification ?
TIA,
-Carlos
Solved! Go to Solution.
01-07-2022 01:59 PM
It allows for a lot more freedom when grouping endpoints. A good example of this is using endpoint identity groups for static whitelists, or using them for iPSK. In both these cases you can have multiple endpoint types that wouldn't share the same profile but need the same treatment from an authz perspective.
01-07-2022 01:59 PM
It allows for a lot more freedom when grouping endpoints. A good example of this is using endpoint identity groups for static whitelists, or using them for iPSK. In both these cases you can have multiple endpoint types that wouldn't share the same profile but need the same treatment from an authz perspective.
01-07-2022 02:09 PM
Great, so a higher order classification it is then.
It surprised me though that as a classification, an endpoint can not belong to more than one group,
and being that Profiled is one of the branches, when an endpoint is moved to GuestEndpoints, you "loose" its original type so to say.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide