The /me endpoint just returns the info of current user based from the session data. It does not point to a table. As to the users table that is 'not found', it may be hidden or protected by the authorization.tableHandler.

This particular config hides the users table and prevents any operation on it. It's the recommended simplest way to prevent unauthorized access to users data, but it also prevents the current users from accessing their own data.

'middlewares' => 'dbAuth,authorization', 'authorization.tableHandler' => function ($operation, $tableName) { return $tableName != 'users'; },

Instead of this, you may try the following to just hide the password column (as well as any other column that you want to hide). Couple it with multiTenancy handler to limit access only to current users' own data. You can also check on the type of $operation to further customize your actions.

'authorization.columnHandler' => function ($operation, $tableName, $columnName) { return !($tableName == 'users' && $columnName == 'password'); },

It seems to override the session values and destroy the session.

I think it doesn't override the session value, rather, the problem maybe due to different session drivers or path @mevdschee ? Like Codeigniter has its own file or even database table to save its session data while php-crud-api also has a different save path for its session.

It seems to override the session values and destroy the session.

I think it doesn't override the session value, rather, the problem maybe due to different session drivers or path @mevdschee ? Like Codeigniter has its own file or even database table to save its session data while php-crud-api also has a different save path for its session.

I made them both to use the PHPSESSID generated by the native session.
The issue is when app is opened CODIGNITER regenerate the session id but when login is called, the API regenerate the SESSION ID and when SESSION Is changed for either of them they again try to re-generate the ID (due to security reasons).

Can you share your use case for this? Maybe, if you are just accessing the php-crud-api endpoints from the codeigniter app, you don't need to maintain user session in the php-crud-api and just use the codeigniter session. It is possible to use apiKeyDbAuth middleware to validate the requests from CI. You just have to retrieve the apiKeyDbAuth.apiKeyColumn when you login to the CI app.