Just trying to setup a connection and don't want to spin my wheels, if its not ready. If its coming up, is it soon? Thanks for any guidance.
One of our developers was given a work around by MattG. I'll use it until the ticket is fully implemented. Sorry for the duplicate contact.
In the current state, it's not possible to see/approve certificates on the Incoming Connections page. This is likely the workaround you already received, but I'll post it here again in case anyone else is running in to it.
- After creating the outgoing connection, on the gateway with the incoming connection, find the certificate on the file system in
data/gateway-network/server/security/pki/rejected. - Move the cert file to
data/gateway-network/server/security/pki/trusted/certs. The gateway should automatically register this change and see the cert as approved. - You should then be able to see/approve the incoming connection back in the UI on the Incoming Connections tab.
2 Likes
I’m troubleshooting a Gateway Network connectivity issue between an 8.3 gateway and an 8.1 gateway.
I tried this setup: 8.3 → outgoing connection → 8.1, moved the .pem file from rejected to trusted on the 8.1 gateway, and approved it — but the gateway connection is still faulted.
As another test, I tried reversing the connection (8.1 → 8.3). On the 8.3 gateway, I noticed the server name in the connection changed from the actual hostnamegbll… to gblx…, and the connection failed.
Are there any other steps or checks I can try to get this connection working?
To confirm, is the Allow Java Serialization enabled? You’ll find this within the Settings of Gateway Network Connections. This setting is off by default on 8.3 and the system will refuse any 8.1 connections until this is on.
is the Allow Java Serialization enabled?
This was it - thank you.
1 Like
Welcome! Glad that ended up doing the trick.