Skip to content
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.

Improve the SecurityErrorEvent message #28

Closed
jbarber opened this issue Jun 2, 2016 · 6 comments
Closed

Improve the SecurityErrorEvent message #28

jbarber opened this issue Jun 2, 2016 · 6 comments

Comments

@jbarber
Copy link
Member

jbarber commented Jun 2, 2016

The error message when failing to connect to the security policy is not very useful:

An security error occurred (Error #2048). Check your policy-policy server configuration or disable security for this domain

We should change this to tell the user what they should do.

@jbarber
Copy link
Member Author

jbarber commented Jun 2, 2016

The message is generated by a SecurityErrorEvent.SECURITY_ERROR event on the socket.

This is described here and here.

The policy is loaded with the code here. Checked with wireshark and it looks like the implementation agrees with the documentation for loadPolicy(). However, the signature for that function doesn't let us know if the policy was successfully loaded or not...

@jbarber
Copy link
Member Author

jbarber commented Jun 2, 2016

#29 addresses this

@jbarber
Copy link
Member Author

jbarber commented Jun 2, 2016

@kristen-allie FYI

@jbarber
Copy link
Member Author

jbarber commented Jun 2, 2016

The message also appears when the VNC port isn't available. But only after the "An IO error occured [sic]" message. Ignore this for now.

@sweeneyapps
Copy link

@jbarber Can you check this out at the forum https://forum.rainforestqa.com/t/a-security-error-occurred-error-2048/1772/31
A tester is having problem w/ 2048 error code.

@jbarber
Copy link
Member Author

jbarber commented Oct 25, 2016

@sweeneyapps my guess is that they don't have connectivity to the server, I'll chase it up in the formum thread

@jbarber jbarber closed this as completed Oct 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants