https://community.checkpoint.com/t5/Endpoint/Remote-Access-clients-configuration-based-on-group-membership/m-p/108397#M3890 <P>Hi All,</P><P>we have to use individual configuration for our ras vpn users. Using check point mobile vpn (windows) client.</P><P>We implemented our requirement with the procedure described in <SPAN><A title=" Remote Access clients configuration based on group membership" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;solutionid=sk114882&amp;partition=Advanced&amp;product=Endpoint" target="_self">sk114882</A>&nbsp;and it works fine. Thus we have some ttm_groups defined on managment server and the corresponding ttm-configfiles on the gateways. </SPAN></P><P><SPAN>As long we have only user objects in the ttm_group everything is working as expected. When adding also usergroups , it will not work for users in that added (nested) group.</SPAN></P><P><SPAN>It looks like that users in a nested group not correctly enforced.</SPAN></P><P><SPAN>How can this behaviour changed, or does a ttm_group not work with nested groups?</SPAN></P><P>&nbsp;</P><P>Any help is highly appreciated!</P><P>&nbsp;</P> Thu, 21 Jan 2021 13:50:35 GMT Markus_Kress 2021-01-21T13:50:35Z https://community.checkpoint.com/t5/Endpoint/Remote-Access-clients-configuration-based-on-group-membership/m-p/108397#M3890 <P>Hi All,</P><P>we have to use individual configuration for our ras vpn users. Using check point mobile vpn (windows) client.</P><P>We implemented our requirement with the procedure described in <SPAN><A title=" Remote Access clients configuration based on group membership" href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;solutionid=sk114882&amp;partition=Advanced&amp;product=Endpoint" target="_self">sk114882</A>&nbsp;and it works fine. Thus we have some ttm_groups defined on managment server and the corresponding ttm-configfiles on the gateways. </SPAN></P><P><SPAN>As long we have only user objects in the ttm_group everything is working as expected. When adding also usergroups , it will not work for users in that added (nested) group.</SPAN></P><P><SPAN>It looks like that users in a nested group not correctly enforced.</SPAN></P><P><SPAN>How can this behaviour changed, or does a ttm_group not work with nested groups?</SPAN></P><P>&nbsp;</P><P>Any help is highly appreciated!</P><P>&nbsp;</P> Thu, 21 Jan 2021 13:50:35 GMT https://community.checkpoint.com/t5/Endpoint/Remote-Access-clients-configuration-based-on-group-membership/m-p/108397#M3890 Markus_Kress 2021-01-21T13:50:35Z