I see there are these two static action_groups that provide this permission: SGS_CREATE_MANAGE_OWN_AUTH_TOKEN and SGS_MANAGE_ALL_AUTH_TOKEN. I’m guessing saving a search requires creating a token somehow under the hood ?
Actually, the auth token feature is completely unrelated to managing searches. I would think that the error message in the logs is just coincidentally logged. Can you check your logs for other items that might be related?
I guess you’re right, there is nothing server side, although I’m not sure on which node the error message ends up.
In the client log (kibana) I see:
GET /api/saved_objects/_find?fields=title&per_page=10&search=%22s%22&search_fields=title&type=search 200 25ms - 9.0B
[security_exception]: no permissions for [indices:admin/mapping/auto_put] and User faxmodem <openid> [requestedTenant=X]
POST /api/saved_objects/search?overwrite=true 403 40ms - 9.0B
The message regarding indices:admin/mapping/auto_put could be an important hint. It seems that Kibana is trying to create a new index here. Just wondering, what index that might be
Could you check the ES logs, whether there is more information?
If not, could you raise the log level for com.floragunn.searchguard.privileges to DEBUG? See here for details in that:
Just one general thought: Does the user have the role SGS_KIBANA_USER? If not, can you try to assign the role to the user?