Connect server returns CORS error, works fine in postman

Hi Joris,

Yes. So we have a frontend that we want to make RESTful requests to persist credentials to 1password, via the connect server endpoints. As I said in my previous post, we have set up the Connect server per the advice of the 1password documentation.

_What I was hoping would happen: _

step 1, A user creates a new set of credentials (email and password) via a web application frontend form with input fields.

step 2, Once the user is happy with these credentials, they submit the form in a POST request to

v1/vaults/vault_id/items

step 3, The credentials are saved to the specific vault (determined by the VAULT_ID) in our company 1password account.

The problem

In step 2, the post request is blocked by CORS. When I was testing the endpoints I saw that it does work from Postman.

I know that creating another server to handle these POST requests would solve the problem, but we would prefer not to have spend extra resources doing so.

Do you have any suggestions for our case?

Thank you for replying,
Rory