You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the dispatcher and jobs must authenticate to Mesos using a [DC/OS
29
-
Service Account](https://docs.mesosphere.com/1.8/administration/id-and-access-mgt/service-auth/).
26
+
When running in [DC/OS strict security mode](https://docs.mesosphere.com/latest/administration/id-and-access-mgt/), both the dispatcher and jobs must authenticate to Mesos using a [DC/OS Service Account](https://docs.mesosphere.com/1.8/administration/id-and-access-mgt/service-auth/).
27
+
30
28
Follow these instructions to authenticate in strict mode:
Where `config.json` contains the following JSON. Replace `<principal>` with the name of your service account, and `<secret_name>` with the name of the DC/OS secret containing your service account's private key. These values were created in Step #1 above.
72
+
73
+
```
74
+
{
75
+
"service": {
76
+
"principal": "<principal>",
77
+
"user": "nobody"
78
+
},
79
+
"security": {
80
+
"mesos": {
81
+
"authentication": {
82
+
"secret_name": "<secret_name>"
83
+
}
92
84
}
93
85
}
94
86
}
95
-
}
96
-
```
97
-
98
-
4. Submit a Job
87
+
```
99
88
100
-
We've now installed the Spark Dispatcher, which is authenticating
101
-
itself to the Mesos master. Spark jobs are also frameworks which must
102
-
authenticate. The dispatcher will pass the secret along to the jobs,
103
-
so all that's left to do is configure our jobs to use DC/OS authentication:
We've now installed the Spark Dispatcher, which is authenticating itself to the Mesos master. Spark jobs are also frameworks which must authenticate. The dispatcher will pass the secret along to the jobs, so all that's left to do is configure our jobs to use DC/OS authentication:
SSL support in DC/OS Spark encrypts the following channels:
115
103
116
-
* From the [DC/OS admin router][11] to the dispatcher
117
-
* From the dispatcher to the drivers
118
-
* From the drivers to their executors
104
+
* From the [DC/OS admin router][11] to the dispatcher.
105
+
* From the dispatcher to the drivers.
106
+
* From the drivers to their executors.
119
107
120
-
There are a number of configuration variables relevant to SSL setup.
121
-
List them with the following command:
108
+
There are a number of configuration variables relevant to SSL setup. List them with the following command:
122
109
123
110
$ dcos package describe spark --config
124
111
@@ -156,20 +143,15 @@ There are only two required variables:
156
143
</tr>
157
144
</table>
158
145
159
-
The Java keystore (and, optionally, truststore) are created using the
160
-
[Java keytool][12]. The keystore must contain one private key and its
161
-
signed public key. The truststore is optional and might contain a
162
-
self-signed root-ca certificate that is explicitly trusted by Java.
146
+
The Java keystore (and, optionally, truststore) are created using the [Java keytool][12]. The keystore must contain one private key and its signed public key. The truststore is optional and might contain a self-signed root-ca certificate that is explicitly trusted by Java.
In addition to the described configuration, make sure to connect the
190
-
DC/OS cluster only using an SSL connection, i.e. by using an
191
-
`https://<dcos-url>`. Use the following command to set your DC/OS URL:
171
+
In addition to the described configuration, make sure to connect the DC/OS cluster only using an SSL connection, i.e. by using an `https://<dcos-url>`. Use the following command to set your DC/OS URL:
192
172
193
173
$ dcos config set core.dcos_url https://<dcos-url>
0 commit comments