Closed brife closed 1 month ago
@brife thank you for your report! Can you please confirm/validate:
--authentication-service [service]
option to use a non-default tree to loginA few valid sample commands:
Standard:
frodo conn add https://platform.example.com/am amadmin Passw0rd
Allow insecure connection (self-signed certs):
frodo conn add --insecure https://platform.example.com/am amadmin Passw0rd
Use a non-default login tree:
frodo conn add https://platform.example.com:9443/am amadmin Passw0rd --authentication-service ldapService
Use a non-default login tree and inject a custom header:
frodo conn add https://platform.example.com:9443/am amadmin Passw0rd --authentication-service ldapService --authentication-header-overrides "{host:'am.example.com:8081'}"
Please note that the host URL always stays the same format.
Also, our 2.0.0 release is only weeks (maybe days) away and 2.x provides many more capabilities and fixes issues that we won't backport to 1.x. Check out our latest release: Frodo CLI 2.0.0-66
Thank you, I should have read the manual. --authentication-service solved my problem
Frodo CLI version
Provide output of
frodo -v
You are running the binary release. Installed versions: cli: v1.0.1 lib: v1.1.0 node: v18.5.0I can’t seem to add connections with parameters, For example,
frodo conn add “https:///am?authIndexType=service&authIndexValue=XXX” --insecure
responds with
Cannot use ‘in’ operator to search for ‘callbacks’ in <!– DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
-->
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">