telefonicaid / telefonicaid/iotagent-node-lib
SECURITY_INFORMATION_MISSING error is missing information
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
I try to setup OPC UA agent with OAuth authentication and I get the following error:
2023-03-07 08:51:11 time=2023-03-07T07:51:11.428Z | lvl=ERROR | corr=70688d7e-4ec4-4040-804a-dc0070d1156c | trans=70688d7e-4ec4-4040-804a-dc0070d1156c | op=IoTAgentNGSI.Devices-LD | from=n/a | srv=gtm_jakob | subsrv=/demo | msg=ORION-001: Connection error creating inital entity in the Context Broker: SecurityInformationMissing {
2023-03-07 08:51:11 name: 'SECURITY_INFORMATION_MISSING',
2023-03-07 08:51:11 message: 'Some security information was missing for device type:undefined'
2023-03-07 08:51:11 } | comp=IoTAgent
Unfortunately, this error doesn't provide any helpful information. Could you improve it by logging somehow real error here: https://github.com/telefonicaid/iotagent-node-lib/blob/ed74c96d0a6b8fe485ef4e428a25aa2b60091b94/lib/services/northBound/restUtils.js#L217
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lib/services/northBound/restUtils.js at the referenced line and trace how SecurityInformationMissing is constructed during the OAuth setup path. Reproduce the reported error and verify that the resulting log exposes the relevant underlying security information instead of device type:undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100