Permissions Violation for Publish does not throw an exception

Steps to repro:

1. Create a user that has these permissions: CLIENT = { publish = { allow: [“sub.>”]} subscribe = “sub.>” }

users = [ {user: client, password: ccc, permissions: $CLIENT} ]

Run the following xUnit test and observe no exception is thrown

[Theory]
       [InlineData("client", "ccc", "BAD!", true)]
       public void PublishPermission(string userName, string password, string subject, bool pass)
       {

           ConnectionFactory cf = new ConnectionFactory();

           var options = ConnectionFactory.GetDefaultOptions();
           options.User = userName;
           options.Password = password;

           using (var connection = cf.CreateConnection(options))
           {

           
               connection.Publish(subject, Encoding.UTF8.GetBytes("Hello"));

               var error = connection.LastError;

           }

       }

[ColinSullivan1]

This is a race condition between processing the error and closing the connection and Publish is non-blocking w/r/t publish errors. If the client detects the closed connection first, it’ll handle things as if the the connection was closed. If the client processes the error first, you’ll get an async error notification if an async error handler is set and LastError would be set.

For this test, if you put a sleep or Flush() after the publish to allow the test time to process the error message, you should see LastEx set.

I don’t believe the server will close the connection on a publish error, I suspect the connection is being closed by dispose when falling out of the using block.

[Drew40B]

I am evaluating how nats client handles permission / publish errors.