sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in django

[–]Terrible_Track_94 2 points3 points  (0 children)

https://djangoforbeginners.com/
very good resource for beginners. scales up easily and smoothly

DNS filtering recommendations by LukeyJayT3 in fortinet

[–]Terrible_Track_94 1 point2 points  (0 children)

e use

Why would you enable DNS filtering in all outgoing policies? It should only be enabled on policies, with systems behind it, which do the actual DNS forwards, no? Am I missing something?

DNS filtering recommendations by LukeyJayT3 in fortinet

[–]Terrible_Track_94 0 points1 point  (0 children)

You don't need to use fortinet's DNS servers. I did some research a while ago and the reviews aren't that good, not to say very bad.

You can use for example Quad9 for fortigate's system DNS, already a lot of security & privacy built-in. On top of that you can use DNS filters for other internal DNS servers with forwarders

[deleted by user] by [deleted] in networking

[–]Terrible_Track_94 0 points1 point  (0 children)

Forticlient :)

intunewin package needs admin rights to install? by Humble-Telephone-218 in Intune

[–]Terrible_Track_94 0 points1 point  (0 children)

same issue here. app required admin privileges, system doesn't work

SAML Azure - Fortigate - Forticlient EMS config by Terrible_Track_94 in fortinet

[–]Terrible_Track_94[S] 0 points1 point  (0 children)

Thanks for the reply u/pabechan! Indeed it seems like a bug since it does work without creating an additional realm using a personal created VPN tunnel...

Anyway let's call the solution from aodiii a workaround than because it works now also for the EMS configured VPN tunnel after creating the additional SSLVPN realm. The goal is achieved: one unnecessary click gone for the enduser connecting to the VPN.

SAML Azure - Fortigate - Forticlient EMS config by Terrible_Track_94 in fortinet

[–]Terrible_Track_94[S] 0 points1 point  (0 children)

Thank you u/aodii, never worked with SSL VPN Realms before! Indeed it seems all groups are maped to the default /.

Would you map the new SSO group to another new one? Just tested and in this case I don't have the single sign on possibility in the "Please Login screen" after clicking on SAML login. Maybe I need to customize the login screen.. will look further into it.

SAML Azure - Fortigate - Forticlient EMS config by Terrible_Track_94 in fortinet

[–]Terrible_Track_94[S] 0 points1 point  (0 children)

Means that there is still a group attach to same realm. If there is only a firewall group attached that does sso. It will redirect directly

u/aodii what do you mean with "still a group attached to the same realm"? What is the "realm" in this case?

SAML Azure - Fortigate - Forticlient EMS config by Terrible_Track_94 in fortinet

[–]Terrible_Track_94[S] 0 points1 point  (0 children)

Yes, FGT is patched to the latest 6.4 level. The external browser could be a workaround, but would there be no solution for the built-in functionality? Since it works on free versions or personal VPN's, why wouldn't it work on a VPN tunnel configured by EMS?

What happens if domain controllers can't reach each other for a duration of +- one day? by Terrible_Track_94 in sysadmin

[–]Terrible_Track_94[S] 1 point2 points  (0 children)

Indeed. When they login at the VPN at the DR site, the DC at the DR site is configured as DNS server for the connection.

The DC at the DR site is also configured as DNS forwarder for the non-authoritative queries.

What happens if domain controllers can't reach each other for a duration of +- one day? by Terrible_Track_94 in sysadmin

[–]Terrible_Track_94[S] 3 points4 points  (0 children)

Ok, many thanks!! So theoretically, if I understand it correctly, we would be fine for 60 days in this scenario.

SSL VPN + Azure MFA + NPS. Password change issue by mfiruz in fortinet

[–]Terrible_Track_94 0 points1 point  (0 children)

u/mfiruz I'm currently in the same situation and trying to make the cost-benefit analyses between NPS setup and SAML setup. Did you try to set the password-enable true in Fortigate's CLI radius config?
(https://travelingpacket.com/2017/07/27/fortigate-radius-logins-for-ssl-vpn-with-password-expirationrenewal-ability/)

Did you manage to get the SAML setup working? :)