telefonicaid / telefonicaid/iotagent-node-lib
authentication keystone
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
Hi,
I'm using Keystone and PEP Proxy to perform authentication on Orion requests.
The PEP Proxy is running on port 1026 and the Keystone on port 5000.
Tests using the x-auth-token in a queryContext request on port 1026 worked correctly.
When using the IoT Agent I put the configuration in the config.js file
Config.authentication = {
enable: true,
host: 'localhost',
port: '5000',
user: 'username',
password: 'password'
};
The configuration file provided below is correct?
When I did a device register, the IoTAgent didn't authentication to get the token.
Does anyone know what it can be?
Thanks in advance.
Best Regards,
Caio Thomas Oliveira
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 with the authentication block in config.js and the device-registration flow, then compare it with the working queryContext request through the PEP Proxy on port 1026. Reproduce the registration attempt and determine whether the IoT Agent requests a Keystone token; done means the cause of the missing authentication is identified and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100