FAC's FTM activation email subject line

[Toshi_Esumi]

Looks like FAC's FTM activation email subject line format seems to be below:

  "FortiToken Mobile FTKMxxxxxxxx Activation on <FAC's Interface IP?>"

Which is different from FortiGate's activation email:

  "FortiToken Mobile Activation on FortiGate"

In our case, the interface IP in the subject line is from port2, which we're using for our internal admin access and remote auth server connections, while all client(FortiGate) accesses come through port1 over the internet. Why does it pick the port2 IP? And more importantly, we don't want to show any IP in the subject line. Can it be replaced with like ".... on FortiAuthenticator"?

Our FAC runs 6.3.3.

Thanks,

Toshi

[amouawad · Accepted solution]

You can change the email subject under System > Administration > Replacement Messages > FortiToken Mobile Activation Email Subject and input whatever you want:

[Toshi_Esumi]

Here they are. Thank you very much.

Toshi

[Toshi_Esumi]

I actually have one further question. By default it seems to have {{:site_name}} in the format, and the preview is showing "fortinet.com". Then how come the actual subject in the email has port2 IP? I guess I have to open a ticket and get looked at by TAC if I want to figure this out. I'm going to remove it and put "on FortiAuthenticator" on so it doesn't matter though.

[amouawad]

I think the site_name variable is taken from the FQDN of the FAC.

I'm guessing if you don't have a FQDN it may just use one of the IP addresses. Do you have a FQDN configured?

[amouawad]

Actually just confirmed this is the case. If you don't have the FQDN configured then it will use the IP address instead. For example I've removed my FQDN and can now see the IP of my FAC instead:

[Toshi_Esumi]

I just tested it and got FQDN in the subject line. Since we have two IPs on port1 and port2, it appears that FAC picks the lowest number (port2 has 10.x.x.x, while port1 has 209.x.x.x).

The the preview of the replacement messages page seems to always show "fortinet.com" regardless the FQDN is configured or not, which is confusing or not helping.

Toshi