Test: fix realm ordering so that node transport clients still work

Original commit: elastic/x-pack-elasticsearch@24b660ac45
This commit is contained in:
jaymode 2015-03-31 11:45:29 -04:00
parent 2db6f4e281
commit f80d49e19c
1 changed files with 3 additions and 1 deletions

View File

@ -53,8 +53,10 @@ public class PkiAuthenticationTests extends ShieldIntegrationTest {
.put(InternalNode.HTTP_ENABLED, true)
.put(ShieldNettyHttpServerTransport.HTTP_SSL_SETTING, true)
.put(ShieldNettyHttpServerTransport.HTTP_CLIENT_AUTH_SETTING, true)
.put("shield.authc.realms.esusers.type", "esusers")
.put("shield.authc.realms.esusers.order", "0")
.put("shield.authc.realms.pki1.type", "pki")
.put("shield.authc.realms.pki1.order", "0")
.put("shield.authc.realms.pki1.order", "1")
.put("shield.authc.realms.pki1.truststore.path", getResource("/org/elasticsearch/shield/transport/ssl/certs/simple/truststore-testnode-only.jks"))
.put("shield.authc.realms.pki1.truststore.password", "truststore-testnode-only")
.put("shield.authc.realms.pki1.files.role_mapping", getResource("role_mapping.yml"))