Log In
Register
Forum
Topic RSS
19:45, EEST
June 27, 2012
Offline
I’m working on security configuration. I’m planning to support None, Basic128Rsa15, and Basic256 policies, and None, Sign, and Sign&Encrypt message modes.
By default, I’m passing all nine combinations of those three to server.setSecurityModes(), and that seems to work okay, although I’m using None/None on the client.
When I change the server configuration to remove None from both lists, and change the client side configuration to Basic128/SignAndEncrypt, I’m seeing a problem when I try to connect with UA Expert:
2013-05-06 15:41:28,560[Non-Blocking-Work-Executor-7] INFO – UATcpServer(/127.0.0.1:52520): /127.0.0.1:43827 connected
2013-05-06 15:41:28,562 [Non-Blocking-Work-Executor-1] WARN – Security policy “http://opcfoundation.org/UA/SecurityPolicy#None” is not supported by the endpoint
2013-05-06 15:41:28,562 [Non-Blocking-Work-Executor-1] INFO – org.opcfoundation.ua.common.ServiceResultException: Bad_SecurityPolicyRejected (code=0x80550000, description=”Security policy “http://opcfoundation.org/UA/SecurityPolicy#None” is not supported by the endpoint”)
It looks like UA Expert is still trying to connect with None. I’ve tried creating a new server in UA Expert, and also different combinations of policy/message security, and I still get this error. Do you see this problem, too, or am I doing something wrong with the client?
6:57, EEST
December 21, 2011
Offline
Yes this is a known problem with the current Java stack. If you disable None-security, the getEndpoints() service, which is done without security to find out the available endpoints, will also fail.
This will be fixed in the new Java stack 1.02, which is already available from the OPC Foundation and we are preparing a beta release of the SDK based on the new stack as well.
If you send email to our support, I can provide you a “preliminary beta” version of the SDK for testing.
1 Guest(s)
