-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use unique substring for commands, must use AM URL #213
Comments
Hello @jgdtech this is peculiar indeed! Could you please run the info command with the debug flag like so:
And post the sanitized output? In case you prefer a private email chain vs public forum to exchange log data, you can drop me a personal message at vscheuber@gmail.com and reference this issue. The debug flag might reveal a little more about what's happening. It appears rather unusual that it would error out this way but work with the full URL. Would love to figure out what's happening here. |
oh, and another option to add to create more clarity:
|
Output of "frodo info --debug --curlirize sand": Error getting cookie name: Error: connect ECONNREFUSED ::1:80 |
Output of "frodo conn describe sand": ConnectionProfileOps.describeConnectionProfile: start |
Ok, this one is still a mystery to me but I will look into it some more. I might ask you to re-run your tests with a more verbose version if I can't duplicate the issue on my side. Thank you for providing the info. The |
… commands, must use AM URL
@jgdtech if you find the time, would you mind running frodo-cli v0.23.1-1 with the |
Welp... I did the following in my git bash on Windows: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:' Node.js v18.15.0 This is the issue reported in #212 :( |
Let me get a correct version here. Going back to v0.23.0 and testing for that issue with #212 ... |
Yep, I see it with v0.23.0, head back a version |
frodo v0.22.0 doesn't have the issue from #212. Can you put the same debugging there for me to use? |
ok, with frodo v.0.22.0 (NPM), I can do the following: This is all within git bash on Windows. |
not quite sure why I ran the binary package before for v0.23.0 ... but ok |
FYI with version v.0.22.3 this is working frodo info dvuse1-dev $ frodo -v |
… commands, must use AM URL
… commands, must use AM URL
Closing. @jgdtech please reopen if you are still struggling with this. |
Frodo CLI version
Provide output of
frodo -v
You seem to be running the binary package
Installed versions:
cli: v0.23.0
lib: v0.18.8
node: v18.5.0
Describe the issue
Cannot use unique substring for "host" as it worked in previous versions and as listed in "frodo conn list" command.
$ frodo conn list
https://openam-xxxsandboxxxxx1.forgeblocks.com/am
Any unique substring of a saved host can be used as the value for host parameter in all commands
$ export AMURL=https://openam-xxxsandboxxxxx1.forgeblocks.com/am
$ frodo conn describe sand
... this works
$ frodo info sand
Error getting cookie name: Error: connect ECONNREFUSED ::1:80
Service account login error: Error: connect ECONNREFUSED ::1:80
$ frodo journey list sand
Error getting cookie name: Error: connect ECONNREFUSED ::1:80
Service account login error: Error: connect ECONNREFUSED ::1:80
$ frodo info $AMURL
... this works
$ frodo journey list $AMURL
... this works, returns list of journeys
OS: tried on Ubuntu 22.04 and Debian 11.6 - both on WSL on Windows 10.
The substring for commands was working on my previous version of frodo v0.16.1 which I ran on Git bash but that's broken now (I see an issue already created for that).
I created a service account and set the ID and key as mentioned in this article: https://community.forgerock.com/t/frodo-service-accounts-secure-ci-cd-in-forgerock-identity-cloud/2065
% export FRODO_SA_ID=1ffa3108-a5de-476a-977f-4432633100ce
% export FRODO_SA_JWK=$(cat ~/Downloads/cicd_privateKey.jwk)
I then created the connection to my ForgeRock Identity Cloud instance using an admin account + pw (MFA is enabled), then entered OTP at prompt.
The text was updated successfully, but these errors were encountered: