I have an on prem AD synced to Entra - my EMS cloud is connected and the
Entra domain is imported over. I have configured SAML so when the client
is pushed to my contractors who are non-domain joined devices, they will
be prompted for credentials bef...
Migrating a customer over to a FortiGate from a watchguard and they
currently have fortiswitches managed via FortiEdge cloud. I want to
migrate the management of these switches to the FortiGate via Fortilink
- what are key things to consider for this...
I have 1 RADIUS group that has 3 Microsoft NPS server IPs
(primary/secondary/tertiary). through the GUI I have successful
authentication to the Primary and am able to use my test user in the
associated AD group. the secondary fails, and I'm unsure of...
This specific issue for me was resolved by copying out the x509 used in
the SAML trace to create a new cert that i uploaded to the EMS - for
whatever reason it was using a different cert to sign then the one
generated at the time of creating the Azur...
EMS cloud is connected the Entra domain - there is no specific ADFS
host. The certificate is what was generated by the custom application
made for the SSO SAML on Azure side....am i missing something?
Right, this makes sense. But I DO have source IP set and what I
described on the initial post when running the first command i can see
on debugs the Fortigate is not sourcing from the specified source in the
radius config when running that specific c...
Here are 2 examples on 2 different Firewalls: v7.2.9
build1688FG200Fconfig user radiusedit "FR-RADIUS"set server
"172.16.189.16"set secret ENC set source-ip
"172.16.188.101"set secondary-server "172.16.177.35"set secondary-secret
ENC nextendSecondary...
