Fortigate client based ssl-vpn with saml group matching
I am testing out client based ssl-vpn using SAML Auth. When I debug saml on the fortigate I see that group that comes back from SAML is correct but I am getting added to the wrong portal.
I have users group configured as per https://docs.fortinet.com/document/fortigate-public-cloud/7.4.0/azure-administration-guide/584456/configuring-saml-sso-login-for-ssl-vpn-with-entra-id-acting-as-saml-idp with:
config user group
edit FortiGateAccess
set member azure
config match
edit 1
set server-name azure
set group-name <object ID>
next
end
next
end
How does the fortigate relate the group name to the portal name?

