Troubleshoot Your Java WebSocket Client

This procedure provides troubleshooting information for the most common issue that occurs when using Kaazing Java WebSocket clients.

Before You Begin

This procedure is part of Checklist: Build Java WebSocket Clients.

Note: Learn about supported browsers, operating systems, and platform versions in the Release Notes.

What Problem Are You Having?

• Kerberos challenge handler not working

Kerberos challenge handler not working

Cause: Kerberos challenge handlers might not work for one or more of the following reasons:

• The client cannot connect to the Kerberos Domain Controller (KDC).

  Solution: Ping the KDC from the computer running the client and the server hosting the Gateway. Also, ensure that you can Telnet to Kerberos port number 88 from both computers (telnet> open KDC-server-name 88).

• The client cannot obtain a Kerberos ticket.

  Solution: Test ticket acquisition by executing the following commands to ensure that the KDC is accessible and able to issue service tickets:

  For Linux:

  $ kinit -t /etc/keytab-name.keytab -S service-instance-name username@KDC-server-name

  For Windows:

  $ kinit username@KDC-server-name

  The output will be:

  Please enter the password for username@KDC-server-name:

  Enter the password, and then enter:

  $ klist

  The ticket cache is displayed along with each ticket's expiration date.

• Service name is in the incorrect format in the Kerberos challenge handler code.

  Solution: The service name should be in the format: HTTP/servergw.hostname.com. See Creating Kerberos Challenge Handlers for examples.

• The pop-up dialog in the client used to obtain user credentials does not ensure that the username format is correct.

  Solution: Ensure that the result of the pop-up dialog used to obtain user credentials is formatted as
  username@KDC-server-name.

Next Step

You have completed the Java client checklist. For more information on client API development, see the Java Client API.