Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

certdnsnames and plchostname not used in the certificate #318

Closed
JeremyTheocharis opened this issue Nov 27, 2023 · 4 comments
Closed

certdnsnames and plchostname not used in the certificate #318

JeremyTheocharis opened this issue Nov 27, 2023 · 4 comments
Assignees

Comments

@JeremyTheocharis
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

docker run --rm -it -p 50000:50000 -p 8080:8080 --name opcplc mcr.microsoft.com/iotedge/opc-plc:latest --pn=50000 --autoaccept --sph --sn=5 --sr=10 --st=uint --fn=5 --fr=1 --ft=uint --gn=5 --plchostname=localhost --showpnjsonph --certdnsnames=localhost

Any log messages given by the failure

2023-11-27_11h46_37

Expected/desired behavior

localhost should show up in the DNS names in the certificate

OS and Version?

Docker Desktop on Windows 11

Versions

docker latest

Mention any other details that might be useful

We are integrating the simulator as test simulator for the open-source project "benthos-umh" (https://github.com/united-manufacturing-hub/benthos-umh). We are troubleshooting why the server is closing the connection unexpectedly, and came up with this smaller problem. Maybe fixing this will solve the larger problem we are working on. If this does not fix our actual problem, we will probably create a separate issue for this.


Thanks! We'll be in touch soon.

@luiscantero
Copy link
Collaborator

Hi, the stack SDK replaces localhost automatically. For your use-case you could do something like this:

docker run --rm -it -p 50000:50000 -p 8080:8080  -h someservername --name opcplc mcr.microsoft.com/iotedge/opc-plc:latest --pn=50000 --autoaccept --sph --sn=5 --sr=10 --st=uint --fn=5 --fr=1 --ft=uint --gn=5 --plchostname=localhost --showpnjsonph

You can also replace someservername above with localhost and it shows in the dnsnames list. Please let me know if this helps.

@luiscantero luiscantero self-assigned this Nov 28, 2023
@luiscantero
Copy link
Collaborator

luiscantero commented Nov 30, 2023

@JeremyTheocharis any updates?

@JeremyTheocharis
Copy link
Author

I can confirm it solved the issue, however the underlying issue is still there. But let me close this one. Thank you for your help!

@luiscantero
Copy link
Collaborator

Thanks for confirming. Could you please open an issue for the OPC UA SDK. Just copy-paste some info from here and post a link to this one. I will make sure that it gets triaged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants