Forum Discussion
unable to verify the first certificate with node.js
Hi David, TMUI (the web GUI listening on port 443) only listens on port 443 and TLS is required. This is the only way to talk to iControl REST from off box.
However, when calling localhost you can call iControl REST directly on port 8100, bypassing TMUI and forgoing the need for TLS. This will work with basic auth, token auth would be possible but would be a different workflow.
One FYI to add about making REST calls to data groups (which you may already know); data groups are collections (vs sub-collections). What this means that if you want to update even one value, your REST call must contain all records including changes (not just the changed records).
Very cool - I didn't know you could do this and it works fine from the console:
curl -uadmin:admin http://localhost:8100/mgmt/tm/ltm/data-group/internal/~acc~dgroup
I made the following change:
var bigip = new iControl({
host: 'localhost',
proto: 'http',
port: '8100',
username: 'admin',
pass: 'admin',
strict: 'false',
debug: 'true'
});
but now get a "HPE_INVALID_CONSTANT" error:
bigip.list dgPath: /ltm/data-group/internal/~acc~dgroup err: { [Error: Parse Error] bytesParsed: 0, code: 'HPE_INVALID_CONSTANT' }
I am true noob using node.js and don't really know how to debug this very well yet. Any suggestions are appreciated.
Thanks,
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com