Skip to content

Commit 6ec1809

Browse files
committed
more
1 parent 3082336 commit 6ec1809

File tree

1 file changed

+2
-2
lines changed
  • x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authc

1 file changed

+2
-2
lines changed

x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authc/Authentication.java

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ public Authentication(
9696
this.metadata = metadata;
9797
if (user.isRunAs()) {
9898
authenticatingSubject = new Subject(user.authenticatedUser(), authenticatedBy, version, metadata);
99-
// The lookup user for run-as currently don't have authentication metadata associated with them because
99+
// The lookup user for run-as currently doesn't have authentication metadata associated with them because
100100
// lookupUser only returns the User object. The lookup user for authorization delegation does have
101101
// authentication metadata, but the realm does not expose this difference between authenticatingUser and
102102
// delegateUser so effectively this is handled together with the authenticatingSubject not effectiveSubject.
@@ -121,7 +121,7 @@ public Authentication(StreamInput in) throws IOException {
121121
metadata = in.readMap();
122122
if (user.isRunAs()) {
123123
authenticatingSubject = new Subject(user.authenticatedUser(), authenticatedBy, version, metadata);
124-
// The lookup user for run-as currently don't have authentication metadata associated with them because
124+
// The lookup user for run-as currently doesn't have authentication metadata associated with them because
125125
// lookupUser only returns the User object. The lookup user for authorization delegation does have
126126
// authentication metadata, but the realm does not expose this difference between authenticatingUser and
127127
// delegateUser so effectively this is handled together with the authenticatingSubject not effectiveSubject.

0 commit comments

Comments
 (0)