[BUG] missing user type in chat

[userInner]

OpenIM Server Version

v0.0.50-alpha.65

Operating System and CPU Architecture

Windows (AMD)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce

Problem description:

Authorization verification of the server gRPC interface failed, and the log showed an error of "missing user type".
Root cause analysis:
After debugging, it was found that the gRPC interceptor (mw.RpcServerInterceptor, version v0.0.50-alpha.65) used on the server side had a defect. It can correctly parse opUserId from the metadata requested by the client and put it into the context, but completely misses the processing of opUserType.
This causes all gRPC calls that need to verify the user type to fail because userType cannot be found in the context.

Repair suggestion:

The code of the interceptor needs to be fixed so that it can correctly handle opUserType and set it to the context when processing the incoming metadata, just like handling opUserId.

Screenshots Link

No response

[mo3et]

I've confirmed that this logic is correct. In the chat repository, you need to assign values to specific Headers by referring to the format of the mw.SetToken function.