Skip to content

Missing Input for Authorization #3

@skwaugh

Description

@skwaugh

Where do you configure Authorization for the Strapi plugin?

The only field during setup is Strapi URL, and the Strapi docs indicate that the API key should be included as a Header:

When performing a request to Strapi’s REST API, the API token should be added to the request’s Authorization header with the following syntax: bearer your-api-token .

Does the Strapi<–>WeWeb plugin use a different (non-REST) endpoint i.e. graphql or something I’m missing?

Because when you create a collection, there is no later opportunity to provide an API Key. See screenshot of the collection wizard -

image
image

When you create a new API key in Strapi, the final confirmation dialogue looks as follows:

Step 3: Completed ✅
See content in action by making an HTTP request:

To this URL: https://<YOUR_DOMAIN>/api/<YOUR_CT> (YOUR_CT = your content-type)
With the header: Authorization: bearer <YOUR_API_TOKEN>
For more ways to interact with content, see the documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions