401 authenticate error

Hi @ireferpesa,

Thanks for reaching out.

To figure our the issue, can you please share the following?

1. What is the exact error response you are getting?
2. Were you able to do the Test Configuration successfully in our plugin?

The above detials will help us resolve the issues you are having.

You can find the code snippet here if you are using the Basic Auth from our plugin.

Looking forward to your reply.

Thanks,
Team miniOrange

Hi,

from postman works correctly. The call from the external application fails.
Among the example codes there is none that works for me, since the page is made in svelte and I make the call from javascript.
But I have tried to put the same variables as in the example.
This is the call code, and the error.

 async function getCaso() {
        const response = await fetch(ruta_api, {
            method:'POST',
            timeout:0,
            processData: false,
            mimeType: "multipart/form-data",
            contentType: false,
            headers:{
                //'authorization': 'Bearer ' + token,
                authorization: 'Basic cm9pc2Nyb2xsOmQzczRycjBsbDAu',
            }
        });
        const string = await response.text();
        const json = string === "" ? {} : JSON.parse(string);
        //console.log(json);

        //return await json;

        if (response.status === 200) {
            return await response.json();
        } else {
            console.log(response);
            throw new Error('Error en la queryyyy');
        }
    }

As you can see the error is in the precall of options because it sends the authenticated.

Access to fetch at 'https://xxxxxx/wp-json/wp/v2/pages' from origin 'https://rs.test:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

Hi @ireferpesa,

Thanks for sharing the error response. It seems you are getting a CORS issue which generally happens when you try to make the request from a JS-based framework (Client side) to the PHP-based WordPress APIs (Server Side).

You can add appropriate configuration rules in your WordPress server config file to remove this.

Please feel free to ask if you need any help on this.

Thanks,
Team miniOrange

could you please elaborate? I tried to add some CORS policies config lines through htaccess as I posted earlier, but to no avail

Hi @ireferpesa,

Thanks for the quick response.

The .htaccess configuration looks good, can we have a quick meet and screen share session to debug this and help you out?

If it works for you, then you can drop the query from the plugin support forum and mention the scenario so we can assign the technical engineers to set up the call and help you further.

Thanks,
Team miniOrange

Hi @ireferpesa,

We haven’t heard back from you in the last couple of days, so we are marking this thread as resolved. You can always post your queries on this forum if you have any questions or face issues with our plugin. We’d be happy to help you.

Thanks,
Team miniOrange