Currently Core stores authentication state (user information) returned from the http.registerAuth hook handler internally and hence it's not available to plugins even to the Security plugin that created the state.
It means that Security plugin should always do additional call to /_security/_authenticate if it wants to get currently authenticated user even though this information is already stored in the core, but just not available to us.
But more importantly during request authentication stage Security would like to store additional Kibana specific information that can't be retrieved from /_security/_authenticate afterwards, e.g. the name/type of the authentication provider that was used to authenticate request (needed for #49865 and potentially for #39313).
This type of information is already available through public Security API so we're not exposing anything extra here.
Ideally Security would like to have access to the state itself and whether or not request was successfully authenticated. That would help us to eliminate unnecessary back-end calls and pave the way to solving more use cases.
Currently Core stores authentication state (user information) returned from the
http.registerAuthhook handler internally and hence it's not available to plugins even to the Security plugin that created the state.It means that Security plugin should always do additional call to
/_security/_authenticateif it wants to get currently authenticated user even though this information is already stored in the core, but just not available to us.But more importantly during request authentication stage Security would like to store additional Kibana specific information that can't be retrieved from
/_security/_authenticateafterwards, e.g. the name/type of the authentication provider that was used to authenticate request (needed for #49865 and potentially for #39313).This type of information is already available through public Security API so we're not exposing anything extra here.
Ideally Security would like to have access to the state itself and whether or not request was successfully authenticated. That would help us to eliminate unnecessary back-end calls and pave the way to solving more use cases.