modify apikey in a provisioned device
AlvaroVega opened this issue · 7 comments
IoT Agent JSON version the issue has been seen with
3.4.0
Bound or port used (API interaction)
Northbound (Provision API and NGSI Interactions)
NGSI version
NGSIv2
Are you running a container?
Yes, I am using a contaner (Docker, Kubernetes...)
Image type
None
Expected behaviour you didn't see
modify apikey in a provisioned device
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Configs
environment:
- "IOTA_CB_HOST=orion"
- "IOTA_CB_PORT=1026"
- "IOTA_NORTH_PORT=4041"
- "IOTA_REGISTRY_TYPE=mongodb"
- "IOTA_MONGO_HOST=mongodb"
- "IOTA_MONGO_PORT=27017"
- "IOTA_MONGO_DB=iotagent-json"
- "IOTA_HTTP_PORT=7896"
- "IOTA_PROVIDER_URL=http://iot-agent:4041"Log output
No response
Hi @AlvaroVega ,
The bug is to provide a functionality to update apikey of a pre-provisioned device.
For Example: A device is provisioned with apikey '123'. Then one should able to change the apikey from '123' to '456' with update API of device provisioning.
Could you please confirm the above understanding of issue?
Your understanding is right.
Hi @AlvaroVega ,
The bug is to provide a functionality to update apikey of a pre-provisioned device.
For Example: A device is provisioned with apikey '123'. Then one should able to change the apikey from '123' to '456' with update API of device provisioning.
Could you please confirm the above understanding of issue?
BTW I'm working on this issue (some works were done in https://github.com/telefonicaid/iotagent-node-lib/tree/task/device_update_handler_with_old_device_value)
BTW I'm working on this issue
Thanks for the information.
Hi @fgalan ,
As mentioned @AlvaroVega is working on this issue. Please confirm if I should work on this issue or he will continue to work.
@Madhu1029 you are right. Sorry for the misunderstanding.