fredoboulo
commented
3 years ago Hi, I apologize for the delay.
Can you share a compilable code pinpointing your problem?
When I recycle the ZAuthTest#testCurveSuccessful, by binding a REQ and connecting a REP, it works.
public void testBindREQConnectREP() throws IOException
{
try (ZContext ctx = new ZContext();
ZAuth auth = new ZAuth(ctx, new ZCertStore.Hasher());
ZMQ.Socket server = ctx.createSocket(SocketType.REQ);
ZMQ.Socket client = ctx.createSocket(SocketType.REP)) {
// Start an authentication engine for this context. This engine
// allows or denies incoming connections (talking to the libzmq
// core over a protocol called ZAP).
// Get some indication of what the authenticator is deciding
auth.setVerbose(VERBOSE_MODE);
// auth send the replies
auth.replies(true);
// Tell authenticator to use the certificate store in .curve
auth.configureCurve(certificateFolder);
// We'll generate a new client certificate and save the public part
// in the certificate store (in practice this would be done by hand
// or some out-of-band process).
ZCert clientCert = new ZCert();
clientCert.setMeta("name", "Client test certificate");
clientCert.setMeta("meta1/meta2/meta3", "Third level of meta");
// wait a second before overwriting a cert, otherwise the certstore won't see that the file actually changed and will deny
// if creating new files, this is not needed
// ZMQ.sleep(1);
clientCert.savePublic(certificateFolder + "/testcert.pub");
ZCert serverCert = new ZCert();
// Create and bind server socket
server.setZapDomain("global".getBytes());
server.setCurveServer(true);
server.setCurvePublicKey(serverCert.getPublicKey());
server.setCurveSecretKey(serverCert.getSecretKey());
boolean rc = server.bind("tcp://localhost:*");
assertThat(rc, is(true));
// Create and connect client socket
client.setCurvePublicKey(clientCert.getPublicKey());
client.setCurveSecretKey(clientCert.getSecretKey());
client.setCurveServerKey(serverCert.getPublicKey());
rc = client.connect(server.getLastEndpoint());
assertThat(rc, is(true));
// By default PUSH sockets block if there's no peer
rc = server.setSendTimeOut(200);
assertThat(rc, is(true));
// Send a single message from server to client
server.send("Hello");
ZAuth.ZapReply reply = auth.nextReply(true);
assertThat(reply.statusCode, is(200));
assertThat(reply.userId, is(clientCert.getPublicKeyAsZ85()));
String message = client.recvStr();
assertThat(message, is("Hello"));
}
}
DavidRobb
I'm trying to use ZAuth to authorise a request reply socket pair where the curveServer is on the REQ socket that 'binds' and waits for the REP socket to connect.
It half works in that the REP socket is authorised and receives a request, then sends a reply. However, the REQ socket never sees this reply.
Setup
REQ CurveServer Config
REP CurveClient Config
Even with client2Sec key correctly set in my key store location, the CurveServer hangs waiting at the line indicated. Rep Client appears to go through the motions of receiving the message and sending the reply.
However, if I have auth configured as ALLOW_ANY it works fine.
Is there something a bit odd about this setup? Usually the CurveServer would be the 'Server' and reply to Client requests with a REP socket. But for this dynamically setup connection I want the CurveClient to be the 'Server' and respond to CurveServer requests.
If I swap the REP and REQ socket types over and send the initial Request from the CurveClient then it also works fine. Hence, I think I have my keys and ZAuth all configured correctly.