Unable to perform initial sync - authentication issues

rh917rh917
Community Member
edited February 11 in Secrets Automation

When setting up the connect server i'm able to generate the 1password-credentials.json file. After ensuring the contents are being read, i receive authorization errors when attempting to execute the command curl -H "Accept: application/json" -H "Authorization: Bearer $OP_API_TOKEN" http://localhost:8080/v1/vaults

The container logs are below:

$ docker-compose up
Creating network "1-password_default" with the default driver
Creating 1-password_op-connect-api_1  ... done
Creating 1-password_op-connect-sync_1 ... done
Attaching to 1-password_op-connect-sync_1, 1-password_op-connect-api_1
op-connect-sync_1  | {"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2022-01-12T22:44:11.695430217Z","level":2}
op-connect-sync_1  | {"log_message":"(I) [discovery-local] starting discovery, advertising endpoint 41301 /meta/message","timestamp":"2022-01-12T22:44:11.695556061Z","level":3}
op-connect-sync_1  | {"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2022-01-12T22:44:11.695670341Z","level":3}
op-connect-sync_1  | {"log_message":"(I) serving on :8080","timestamp":"2022-01-12T22:44:11.695704746Z","level":3}
op-connect-sync_1  | {"log_message":"(I) no existing database found, will initialize at /home/opuser/.op/data/1password.sqlite","timestamp":"2022-01-12T22:44:11.695953598Z","level":3}
op-connect-sync_1  | {"log_message":"(I) database initialization complete","timestamp":"2022-01-12T22:44:11.700799865Z","level":3}
op-connect-sync_1  | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2022-01-12T22:44:11.701005577Z","level":3}
op-connect-api_1   | {"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2022-01-12T22:44:11.714818649Z","level":2}
op-connect-api_1   | {"log_message":"(I) [discovery-local] starting discovery, advertising endpoint 41193 /meta/message","timestamp":"2022-01-12T22:44:11.714853682Z","level":3}
op-connect-api_1   | {"log_message":"(I) starting 1Password Connect API ...","timestamp":"2022-01-12T22:44:11.715014971Z","level":3}
op-connect-api_1   | {"log_message":"(I) serving on :8080","timestamp":"2022-01-12T22:44:11.715034627Z","level":3}
op-connect-api_1   | {"log_message":"(I) established incoming bus peer connection","timestamp":"2022-01-12T22:44:11.715697729Z","level":3}
op-connect-api_1   | {"log_message":"(I) GET /v1/vaults","timestamp":"2022-01-12T22:44:37.272403244Z","level":3,"scope":{"request_id":"3f1da6cc-a5ed-474b-999d-8c8d0502d057"}}
op-connect-api_1   | {"log_message":"(I) GET /v1/vaults completed (401: Unauthorized)","timestamp":"2022-01-12T22:44:37.272847797Z","level":3,"scope":{"request_id":"3f1da6cc-a5ed-474b-999d-8c8d0502d057"}}

System Info:

OS: CentOS 8
Architecture: AMD64
Platform: Docker version 20.10.12, build e91ed57


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

Comments

  • Joris_1PJoris_1P

    Team Member

    Hi @rh917,

    Apologies for the late response. I am not sure if you are still running into these issues. But if you are: could you share the response that you are getting on the curl? There may be a hint in there as to what is going wrong.

This discussion has been closed.