Comment on page
The impersonation feature is intended for ROR administrators, rather than users. We can point out the two most obvious use cases when the admin could take advantage of the feature:
Let's imagine that some user has a problem with their ROR configuration (eg. the user doesn't have access to some feature that was blocked at ROR's level by you, the admin). And they are not able to clearly describe what the issue is (sounds familiar?). As an administrator, it would be extremely beneficial if you could see what the user sees. Thanks to the impersonation feature, an admin is allowed to impersonate the user and experience exactly what the user experiences.
When an admin configures a new user in ROR settings, they face two problems:
Will the updated configuration break the production cluster?
How do I know that the new user is correctly configured? Did I configure all their permissions correctly??
Both of the problems can be solved using the ROR's impersonation. Thanks to the fact that the impersonation feature always uses its own Test Settings, that is completely independent from the main production settings, the admin can alter it without worries that their actions will break something and users won't be able to do their job.
Admin can add the new user configuration without worrying and then test it by impersonating the user. They can check if the user can log in without problems and if the user has access only to the Kibana features the admin wanted to grant. When the admin is sure that everything is configured correctly, they can promote the settings (test) to production.
Before an admin will be able to impersonate a user, they have to configure ROR properly. The configuration consists of several parts:
When you call Elasticsearch directly or through ROR Kibana, ROR ACL is defined by Settings (we can assume they are Main Settings). The Test Settings define another ACL, that is taken into consideration by ROR ES only when a proper impersonation header is passed. The header is managed by ROR internally. The Test Settings are active only for a strictly defined amount of time (by default it's 30 minutes, but the admin can change it before applying Test Settings). After the time has expired, they are automatically invalidated (for security reasons). Obviously, the admin is allowed to invalidate the configured Test Settings in any time. There is no way to have more than one Test Settings configured at time.
But copying Main Settings as Test Settings is not enough. We also have to instruct ROR which users can be considered as impersonators (the ones, who are allowed to impersonate other users). The list of allowed impersonators and users they can impersonate are defined in the
impersonationsection in ROR Settings:
- impersonator: admin1 // Who can impersonate? (user name or pattern)
users: ["*"] // Who can be impersonated? (user names or patterns)
auth_key: admin1:pass // Authentication rule required to impersonate (any authentication rule can be used here)
- impersonator: admin2
In the example above, we see that we have two impersonators:
admin2. The first one can impersonate any user (
*) and they are able to authenticate using basic auth (
admin1:pass). The second impersonator can impersonate only
dev2user. They will be authenticated using
When an impersonator passes wrong credentials ROR will tell Kibana that impersonation is not allowed.
ROR has many sophisticated authentication & authorization methods. Some of them are based on external systems like LDAP. The problem with such systems, in regard to to the impersonation feature, is that those systems either don't support it by default or don't support it at all and even if they do - the configuration is complex.
That's why we decided to solve it totally differently - using mocks. Wikipedia defines
an imitation, usually of lesser quality.And in the case of external authentication systems we are going provide an imitation of it that will tell ACL which users should be successfully authenticated by it. When we consider an authorization service, a mock of it will return the ACL users with their roles in the service. And this is enough for ROR to support impersonation.
How does ROR use the mocks? Let's suppose we have an
ldap_authrule. When ROR processes the rule, it:
- asks the given LDAP service if the username can be authenticated with a given password, and if they can ...
- asks LDAP to list what groups the user belongs to
In the impersonation case, it looks pretty much the same. The difference being that ROR won't call any LDAP server - the mock will provide the required information instead (no password required). During impersonating, when ROR processes an LDAP rule, it:
- asks the mock if the username exists, and if it does ...
- asks the mock to tell what groups the user belongs to
⚠️ IMPORTANT: If one or more of the external services are not mocked, ROR might inform Kibana that the impersonation is not supported. It's better to always define all mocks, to avoid the "Impersonation not supported" Elasticsearch response.
Now that we have configured Test Settings and External Services Mocks, we can try to impersonate a user. In Elasticsearch ROR Settings, user can be:
- provided statically (defined in the settings),
- provided dynamically:
- from external, dependant systems (like LDAP) - we mock them
- from upstream systems (eg. through headers) - they are not known upfront
It means that we pick the users defined in Settings or Mocks, but also we can enter the username and try to impersonate such user.
In Elasticsearch logs, in
USRfield, if an admin user finds something like this:
admin1 as (user1)- it means that
admin1was authenticated and they are the impersonator who is impersonating
All logs of impersonated user in Kibana will have this format
[<log level>][plugins][ReadonlyREST][<filename>][impersonating <impersonated user username>]
When auditing is enabled, the audit document is going to contain an
Impersonation mode has some limitations. Please check if they have an impact on your use cases:
- Not all features available in the ROR configuration are testable with impersonation mode. Some rules used in ROR ACL do not support impersonation. For example, auth rule with hashed credentials (e.g.
auth_key_sha512) can be used in impersonation mode only when credentials follow the format
USER_NAME: HASH(PASSWORD); A fully hashed username and password don't allow fetching a username. The auth rule in such a format won't match during impersonation. In the rules description section you can find information about each rules impersonation support.
- Test Settings are stored in the memory of the node that handled the saving request sent by ROR Kibana plugin. Impersonation support will be limited to this node. We are going to improve it in the future, but for now your Kibana should only communicate with one Elasticsearch node.
- Sometimes it is impossible to fetch usernames defined in the Test Settings. If a
usersrule contains a username pattern with a wildcard, to impersonate a user matching the pattern, you need to enter the username manually.readonlyrest:access_control_rules:- name: "LDAP group g1"type: allowgroups: ["g1"]users:- username: "admin*" // To impersonate a user with a username matching 'admin*' you need to enter the username manually, like 'admin123'groups:- g1: group1ldap_auth:name: "ldap1"groups: ["group1"]ldaps:- name: ldap1[..]impersonation:[...]
- Impersonator - someone who imitates or copies the behavior or actions of another,
- Impersonation - imitating behaviors or actions of a given user,
- Main Settings - the ROR's settings that apply to ACL that handles requests during regular sessions (not the impersonation ones),
- Test Settings - the ROR's settings that apply to ACL that handles impersonating requests (the ones during impersonation session),
- External Service Mock - an imitation of an external service (the supported ones: LDAP, an external authentication service, an external authorization service).