Technical Tip: Custom launcher for VNC password-only access without username

Most VNC solutions are designed for direct connections, based on a client-server approach between the VNC Client and the VNC Server, with the client able to reach the server directly. These classic VNC solutions in Windows and Linux environments traditionally require only a password for remote access, and do not prompt for a username.

MacOS systems running VNC Server software offer the additional ability to provide MacOS credentials (username and password) for remote access from the VNC Client.

In addition, some 3rd party VNC solutions provide cloud-based connectivity options, where logging in to the destination VNC server is made through 3rd party cloud-proxied VNC connections, and in those cases, a full set of credentials (username and password for the cloud service) is needed.

Default FortiPAM VNC templates come with a username field as well as a password field; by default, there is no specific secret template available that would not include the Username field.

A custom VNC secret template can be created, as in the following example, with only the destination IP address (Target) and password fields present:

config secret template
    edit "Nousername_VNC_test"
        config field
            edit "Target"
                set type target-address
            next
            edit "Password"
                set type password
            next
        end
        config launcher
            edit 1
                set launcher-name "TightVNC"
                set port 5900
            next
            edit 2
                set launcher-name "VNC Viewer"
                set port 5900
            next
            edit 3
                set launcher-name "Web VNC"
                set port 5900
        end

    end

    set server-info Others
end

A detailed list of available authentication methods per target Operating System can be found in the following article:
Technical Tip: Authentication methods available in FortiPAM to connect to destination VNC servers