Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Run prettier on authentication-methods.md. 

The new sections of this file were rebased past the addition of
running prettier on these files.
This commit is contained in:
Tim Abbott 2021-09-10 13:23:09 -07:00
parent c9063870d0
commit 908e1e6d19
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/production/authentication-methods.md
View File

@ -551,6 +551,7 @@ to the root and `engineering` subdomains:
`<ds:X509Certificate>[...]</ds:X509Certificate>`). `<ds:X509Certificate>[...]</ds:X509Certificate>`).
Save the certificate in a new `{idp_name}.crt` file constructed as follows: Save the certificate in a new `{idp_name}.crt` file constructed as follows:
``` ```
-----BEGIN CERTIFICATE----- -----BEGIN CERTIFICATE-----
{Paste the content here} {Paste the content here}
@ -558,12 +559,14 @@ to the root and `engineering` subdomains:
``` ```
4. If you want to sign SAML requests, you have to do two things in Keycloak: 4. If you want to sign SAML requests, you have to do two things in Keycloak:
1. In the Keycloak client settings you setup previously, open the 1. In the Keycloak client settings you setup previously, open the
`Settings` tab and **enable** `Client Signature Required`. `Settings` tab and **enable** `Client Signature Required`.
2. Keycloak can generate the Client private key and certificate 2. Keycloak can generate the Client private key and certificate
automatically, but Zulip's SAML library does not support the automatically, but Zulip's SAML library does not support the
resulting certificates. Instead, you must generate the key and resulting certificates. Instead, you must generate the key and
certificate on the Zulip server and import them into Keycloak: certificate on the Zulip server and import them into Keycloak:
1. Generate **Zulip server public certificate** and the corresponding **private key**: 1. Generate **Zulip server public certificate** and the corresponding **private key**:
```bash ```bash
openssl req -x509 -newkey rsa:2056 -keyout zulip-private-key.key \ openssl req -x509 -newkey rsa:2056 -keyout zulip-private-key.key \
@ -571,6 +574,7 @@ to the root and `engineering` subdomains:
``` ```
2. Generate a JKS keystore (replace `{mypassword}` and 2. Generate a JKS keystore (replace `{mypassword}` and
`{myalias}` in the `keytool` invocation): `{myalias}` in the `keytool` invocation):
```bash ```bash
openssl pkcs12 -export -out domainname.pfx -inkey zulip-private-key.key -in zulip-cert.crt openssl pkcs12 -export -out domainname.pfx -inkey zulip-private-key.key -in zulip-cert.crt
keytool -importkeystore -srckeystore domainname.pfx -srcstoretype pkcs12 \ keytool -importkeystore -srckeystore domainname.pfx -srcstoretype pkcs12 \
@ -582,6 +586,7 @@ to the root and `engineering` subdomains:
it on a Mac, you may want to use the keychain it on a Mac, you may want to use the keychain
administration tool to generate the JKS keystore with a UI instead of administration tool to generate the JKS keystore with a UI instead of
using the `keytool` command. (see also: https://stackoverflow.com/a/41250334) using the `keytool` command. (see also: https://stackoverflow.com/a/41250334)
3. Then switch to the `SAML Keys` tab of your Keycloak 3. Then switch to the `SAML Keys` tab of your Keycloak
client. Import `domainname.pfx` into Keycloak. After client. Import `domainname.pfx` into Keycloak. After
importing, only the certificate will be displayed (not the private importing, only the certificate will be displayed (not the private