A TCP/UDP service to launch PuTTY as an SSH client was working well with PAM 2.8.2 but failed to launch after upgrade to 2.8.3.
It turned out that one of the tokens that are translated at run time had one character entered with the wrong case. Specifically our "Client Application" string included <First port> rather than <First Port>. This did not cause a problem prior to 2.8.3 but does not. Changing the string to match the token in the example string case sensitive resolved the problem. For Web Portals the "Launch URL" string may have the same problem.
Configure your services consistently using <Local IP> and <First Port> with the correct case and you should not have a problem.