This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XGS 19.6: AD user prefetch icl. Mail attribute

Hello,

In Sophos UTM SG there was a user prefetch - I am really missing this feature because I need to send quarantine-mails to every user on our on-prem exchange. 

Can´t believe that this is not longer implemented and users are only created when they login the first time?

There is no need for any of our users to logon at our firewall.

VPN is not needed because every modern OS has its own client an we do roll out  fully configured devices.

WebProxy is transparent.

Mail-Release-Self-service becomes a henn-egg-problem: If there is no user, there will be no mail-address to send a quarantine report to inform that user that he has to login into the XGS to release a mail. 

So how can we create/change users in our AD and can publish that to XGS automatically? (push or pull)

I do not believe that the XGS became worse than old SG/astaro.



This thread was automatically locked due to age.
  • So - as far as i recall - SFOS does not create users based on an Authentication process of IPsec VPN due the integration of groups there. This means, back in the day (prior to the group support) you had to create the user first. This never changed, we still need the user first, we simply replaced the need of selecting all users with the group. But still it needs to exists in the first place. 

    But: The backend membership groups should be updated, which is odd to me. Can you post some screenshots of the logviewer - authentication and your AD, which shows this user be in the group you imported? 

    It is important: The name has to match the name in SFOS. Did you import it from the AD? 

    __________________________________________________________________________________________________________________

  • Hi Toni,

    I am back from holiday an fixed the updated additional groupmembership - so that is working.

    Still anyone (!) who is in our AD is able to login into user portal authenticated against RADIUS and can do L2TP.

     

    So the question is:

    How can I do a firewall rule to DENY access for users which are NOT member of the VPN group "VPN-users"?

    I tried to add No1 rule: If member of VPN-group THEN ALLOW VPN=>LAN/DMZ

    and added No2 rule: DENY VPN=>DMZ/LAN

    in the hope that if No1 does not match automatically No2 comes in places - but this did not the trick. Anyone with VPN cann get to systems in DMZ/LAN regardless of being member of "VPN-users".

    So what should I set up?

    Thank you & Cheers - Chris

  • Finally I found a solution for my initial question and the question about authenticating L2TP to AD user group:

    1.) On the RADIUS Server:

    make sure there is a network rule which includes both:
    - AD group membership "VPN users" AND

    - client IPv4 address from the XGS

    Make sure there is no other rule like "all authenticated windows users" later enabled.

    Make sure there is no other rule with no combined group AND client-IP address (e.g. for WLAN auth...)

     

    2.) On XGS:

    - configure AD Authentication server with

    "Display name attribute" = "displayname" and

    "Email address attribute" = "mail"

    - The FIRST AD group you have to import must be ""VPN Users"

    - Under "Authentication" - "Services" change the default group to "VPN users"

    - configure the RADIUS Authentication server

    - put the RADIUS Authentication Server at the first line for Firewall and IPSEC/L2TP

    Now I can confirm that:

    1.) Non existent users (on the XGS) with NO AD membership of "VPN users" cannot authenticate within a L2TP connection attempt

    2.) Non existent users (on the XGS) WITH AD membership of "VPN users" can authenticate within a L2TP connection attempt

    3.) As soon as they connected with L2TP for the first time the users is created on the XGS, the AD group membership is visible under "Other group memberships" AND, tadaaa: with the correct E-mail address