FortiNAC
NOTE: FortiNAC is now named FortiNAC-F. For post-9.4 articles, see FortiNAC-F. FortiNAC is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks.
cmaheu
Staff
Staff
Article Id 197633
Description
When self registration requests are sent to sponsors, the email messages contain links for the sponsor to either automatically accept or deny the request, or to login to the admin UI to do this.  The link contained in the email is composed by FortiNAC and contains the URL of the FortiNAC Server or Control Server.  The FQDN is based on the hostname of the appliance.  In some situations, however, that name may not be desired depending upon the appliance configuration:
  • High Availability
  • SSL certificate subject names differ from Control Server hostname




Solution
To configure FortiNAC to use a specific FQDN in the email links, a property file must be modified on the FortiNAC Server via CLI.  If assistance is required, contact Support.

Modify the property file as follows on both Primary and Secondary Servers:
1. Log into the CLI as root on your FortiNAC Server or Control Server.
2. Navigate to the following directory:
/bsc/campusMgr/master_loader/
3. Using vi or another editor, open the .masterPropertyFile file.
4. At the top of the file there is a sample entry that is commented out. Follow the syntax of the sample entry to create your own changes using one of the following
examples:


FQDN for Links Using HTTPS (Port 8443)
To configure email links to use the FQDN of the FortiNAC Server or Control Server and use https and port 8443 add the information to the EmailLink Host property.

FILE_NAME=./properties_plugin/selfRegRequest.properties
{
com.bsc.plugin.guest.SelfRegRequestServer.EmailLinkHost=https://mySpecialHost.Fortinetnetworks.com:8443
}


FQDN for Links Using HTTP (Port 8080)
To configure email links to use the FQDN of the FortiNAC Server or Control Server add the information to the EmailLinkHost property.

FILE_NAME=./properties_plugin/selfRegRequest.properties
{
com.bsc.plugin.guest.SelfRegRequestServer.EmailLinkHost=http://mySpecialHost.Fortinetnetworks.com:8080
}




Example:

#############################################################
#  FILE_NAME=./properties_plugin/bridgeManager.properties
#  {
#      com.bsc.plugin.bridge.BridgeManager.verifyRegisterdClients=true
#  }
#############################################################
FILE_NAME=./properties_plugin/selfRegRequest.properties
{
com.bsc.plugin.guest.SelfRegRequestServer.EmailLinkHost=https://myNACServer.Fortinetnetworks.com:8443
}



5. Save the changes to the file.
6. Restart the FortiNAC Server.
shutdownCampusMgr
<wait 30 seconds>
startupCampusMgr

When the server restarts, the changes listed in the .masterPropertyFile are written to the selfRegRequest.properties file.


Verify:
Log into the CLI of the FortiNAC Server or Control Server and verify that the changes have been written to selfRegRequest.properties.  At the prompt type
grep -i EmailLinkHost /bsc/campusMgr/master_loader/properties_plugin/selfRegRequest.properties

 

Contributors