Skip to content

Commit 2de9a42

Browse files
committed
refresh JumpCloud IdP
1 parent 2ef9f57 commit 2de9a42

File tree

2 files changed

+29
-66
lines changed

2 files changed

+29
-66
lines changed
Binary file not shown.

src/content/docs/cloudflare-one/identity/idp-integration/jumpcloud-saml.mdx

Lines changed: 29 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -1,93 +1,56 @@
11
---
22
pcx_content_type: how-to
3-
title: Jumpcloud (SAML)
3+
title: JumpCloud (SAML)
44
---
55

6-
JumpCloud provides [Directory-as-a-Service](https://jumpcloud.com/daas-product/) to securely connect user identities to systems, apps, files, and networks. Cloudflare Access integrates with JumpCloud using the SAML protocol. [This documentation from JumpCloud](https://support.jumpcloud.com/s/article/getting-started-applications-saml-sso2) can help you configure applications within your JumpCloud deployment.
6+
[JumpCloud](https://jumpcloud.com/#platform) provides SSO identity management. Cloudflare Access integrates with JumpCloud as a SAML identity provider.
77

8-
These steps focus on requirements specific to Cloudflare Zero Trust.
8+
## Set up Jumpcloud as a SAML provider
99

10-
## Set up Jumpcloud SAML
10+
1. In the [JumpCloud Admin Portal](https://console.jumpcloud.com/#/home), go to **SSO Applications**.
1111

12-
To set up JumpCloud SAML as your identity provider:
12+
2. Select **Add New Application**.
1313

14-
1. Generate a SAML certificate.
14+
3. In the search bar, enter `Cloudflare` and select the **Cloudflare Access** application.
1515

16-
**Tip:** JumpCloud requires that you provide your own certificates for signing SAML assertions. Self-signed certificates are acceptable.
16+
4. Select **Next**.
1717

18-
If you do not have a certificate, this command generates one using OpenSSL:
18+
5. In **Display Label**, enter an application name.
1919

20-
```sh
21-
openssl genrsa -out samlidp.key 2048 ; openssl req -new -x509 -sha256 -key samlidp.key -out samlidp.crt -days 1095
22-
```
20+
6. Select **Save Application**.
2321

24-
```sh output
25-
Generating RSA private key, 2048 bit long modulus
26-
.................................................................................+++++
27-
......................+++++
28-
e is 65537 (0x010001)
29-
```
22+
7. Review the application summary and select **Configure Application**.
3023

31-
When asked to enter a Distinguished Name or a DN to incorporate into your certificate request, you can leave some of these fields blank. Some fields have a default value. Enter a dot (`.`) in the field to leave it blank. For example:
24+
8. In the **SSO** tab, configure the following settings:
25+
1. In **IdP Entity ID**, enter your Cloudflare team domain:
3226

33-
```txt
34-
-----
35-
Country Name (2 letter code) [AU]:.
36-
State or Province Name (full name) [Some-State]:.
37-
Locality Name (eg, city) []:.
38-
Organization Name (eg, company) [Internet Widgits Pty Ltd]:.
39-
Organizational Unit Name (eg, section) []:.
40-
Common Name (e.g. server FQDN or YOUR name) []:JumpCloud SAML IdP
41-
Email Address []:
42-
```
27+
```txt
28+
https://<your-team-name>.cloudflareaccess.com/
29+
```
30+
You can find your team name in Zero Trust under **Settings** > **Custom Pages**.
4331

44-
2. In JumpCloud, select **Applications** in the left-side menu.
32+
2. Set both **SP Entity ID** and **ACS URL** to the following callback URL:
4533

46-
3. Select the + icon at the top-left of the screen to add an application.
34+
```txt
35+
https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
36+
```
37+
3. Scroll up to **JumpCloud Metadata** and select **Export Metadata**. Save this XML file for use in a later step.
4738

48-
4. Choose the **SAML** option in **Application Types**.
39+
9. In the **User Groups** tab, [assign user groups](https://jumpcloud.com/support/get-started-applications-saml-sso#managing-employee-access-to-applications) to this application.
4940

50-
5. Enter an application name in **Display Label**.
41+
10. Select **Save**.
5142

52-
6. Enter an IdP entity in the **IDP IDENTITY ID** field.The IdP entity can be anything, but must be unique. We suggest you reference something identifiable, such as your Cloudflare team domain (`https://<your-team-name>.cloudflareaccess.com/`).
43+
11. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Authentication**.
5344

54-
7. At the prompt, enter the IdP private key and IdP certificate you previously generated.
45+
12. Under **Login methods**, select **Add new**.
5546

56-
8. Set both the **SP entity ID** and **ACS URL** to the following callback URL:
47+
13. Select **SAML**.
5748

58-
```txt
59-
https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback
60-
```
49+
14. Upload your JumpCloud XML metadata file.
6150

62-
You can find your team name in Zero Trust under **Settings** > **Custom Pages**.
51+
15. Select **Save**.
6352

64-
9. Under **SAML SUBJECT NAMEID**, choose **email**.
65-
66-
10. Set the **SAML SUBJECT NAMEID FORMAT** to:
67-
68-
```txt
69-
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
70-
```
71-
72-
11. Under USER ATTRIBUTES enter `email` for the name and `email` for the value.
73-
74-
12. Leave other settings at default.
75-
76-
13. Select **save**. Remember to assign this application to users or groups.
77-
78-
![JumpCloud Application dialog with group added to application](~/assets/images/cloudflare-one/identity/jumpcloud/jumpcloud-saml-2.png)
79-
80-
14. In Zero Trust, go to **Settings** > **Authentication**.
81-
82-
15. Under **Login methods**, select **Add new**.
83-
84-
16. Select **SAML**.
85-
86-
17. Input a **Name**, a **Single Sign on URL**, **IdP Entity ID or Issuer URL**, and **Signing Certificate**.
87-
88-
18. Select **Save**.
89-
90-
To test that your connection is working, go to **Authentication** > **Login methods** and select **Test** next to the login method you want to test.
53+
You can now [test your connection](/cloudflare-one/identity/idp-integration/#test-idps-in-zero-trust) and create [Access policies](/cloudflare-one/policies/access/) based on the configured login method and SAML attributes.
9154

9255
## Example API configuration
9356

0 commit comments

Comments
 (0)