[Bug]: Strategy: "apiToken"

[foodiecompany]

What issue are you experiencing?

The apiToken strategy encounters issues when modifying specific data, and the cause of this problem is currently unknown. However, a workaround is available by switching to the JWT strategy, which allows the messages for changes to function as expected. Your assistance in resolving this matter would be greatly appreciated. Thank you.

Steps To Reproduce

CMS Strapi

Plugin config

const config = {
  io: {
    enabled: true,
    config: {
      socket: {
        serverOptions: {
          cors: {
            origin: [env("CLIENT_URL"), env("STAFF_URL")],
            methods: ["GET", "POST"],
            credentials: true,
          },
        },
      },
      contentTypes: [
        "api::table.table",
        "api::request-staff-event.request-staff-event",
        "api::order.order",
        "api::cart.cart",
      ],
      events: [
        {
          name: "connection",
          handler: ({ strapi }, socket) => {
            strapi.log.info(`[io] new connection with id ${socket.id}`);
          },
        },
      ],
    },
  },

}

Token Configuration

FrontEnd NextJS

const so = io(config.apiUrl, {
    withCredentials: true,
    auth: {
      strategy: "apiToken",
      token: getConfig().guestToken
    }
  });

Networking

Payload

Responce

Comunications

What version of the plugin are you using?

2.0.5

What strapi version are you using?

4.17.1

[ComfortablyCoding]

Thanks for the report! Can you expand on what you mean by "The apiToken strategy encounters issues when modifying specific data"? The reproduction steps are not so clear to me.

How are you sending/modifying the data? What are you expecting to receive back vs what you actually receiving? Is their any custom function that is handling it server side? Any other possible relevant info?

[foodiecompany]

Sure,
When the auth type jwt all works fine but, when I change to apiToken does.

As previously mentioned, we have a collectionType: api::table.table, containing fields like no, descriptions, status, etc.. Everything functions correctly when modifying the 'status' field under the 'jwt' strategy. However, issues arise when using the 'apiToken' strategy.

[ComfortablyCoding]

What "issues" arise when using apiToken? "Issues arise" is a fairly broad term and hard to attempt to reproduce.

[foodiecompany]

Our attached handler is not being called

Example:

socket.on("table:update", (table) => {

});

The event table:update is not triggered when we use the apiToken strategy.

[ComfortablyCoding]

Thank you for the clarification, I will see if I can reproduce this issue

[maxval1]

Additionally, we have webhooks.populateRelations set to true because of this issue: #82

[codyparnell]

I found the cause of this issue, as i was running into the same problem.

I created a pull request with my fix

Basically this was an issue that only effected api tokens with an unlimited duration. The solution was properly querying these tokens.

[ComfortablyCoding]

Thanks Cody! This should be fixed via #87 in the latest relase (v2.0.6)

[foodiecompany]

Thanks!!