$TOKEN and $TOKENID don't work #1

Closed
opened 2023-01-09 23:25:43 +00:00 by missytake · 2 comments
Collaborator

Steps to Reproduce

  1. I created a new authorization token in the web interface
  2. According to README.md, I tried setting TOKENID="token-7xxxx5" and TOKEN="fxxxxxx5-dxxx-4xxx-8xxx-3xxxxxxxx5f0" in my .env
  3. Then I ran ./authorization.sh

Expected Behavior:

I expected to receive a "Login OK".

Actual Behavior:

I got a Login Failed output. When I changed the variable names to SIPUSER and SIPPWD, it suddenly worked.

## Steps to Reproduce 1. I created a new authorization token in the web interface 2. According to README.md, I tried setting `TOKENID="token-7xxxx5"` and `TOKEN="fxxxxxx5-dxxx-4xxx-8xxx-3xxxxxxxx5f0"` in my `.env` 3. Then I ran `./authorization.sh` ## Expected Behavior: I expected to receive a "Login OK". ## Actual Behavior: I got a `Login Failed` output. When I changed the variable names to `SIPUSER` and `SIPPWD`, it suddenly worked.
Poster
Collaborator

In authorization.sh, the curl statement uses --user $SIPUSER:$SIPPWD, not --user $TOKENID:$TOKEN - the README.md should remove the recommendation to call the variable TOKEN*.

In `authorization.sh`, the curl statement uses `--user $SIPUSER:$SIPPWD`, not `--user $TOKENID:$TOKEN` - the README.md should remove the recommendation to call the variable `TOKEN*`.

The code to make both variants work was in the wrong place…

The code to make both variants work was in the wrong place…
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gandalf/Sipgate-CLI#1
There is no content yet.