Hi Team, we're trying to configure our authentication with Gooddata Cloud as OIDC via JumpCloud. We've previously configured it with both Google and Auth0, but we cannot get it to work with JumpCloud. I know its not officially tested, but do you have any customers who have successfully set it up ? Alternatively, is it possible to use SAML ?

Based on the knowledge sources, I can provide you with information about both JumpCloud OIDC and SAML authentication options for GoodData Cloud. ## JumpCloud OIDC Setup While JumpCloud is not officially listed as a tested provider, there is evidence of users attempting to set it up. According to a [community discussion](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1717513056802769?thread_ts=1717513056.802769), here are some key configuration points: Important Configuration Requirements: 1. Redirect URI: Should be

https://<organization-hostname>/login/oauth2/code/<organization-hostname>

2. Login URL: Should be the same as your GD Cloud hostname 3. Client Authentication Type: GoodData does not support "Public (None PKCE)". You must use either: - Client Secret POST (client authorizes by providing the secret in HTTP request body as a form parameter) - Client Secret Basic (uses HTTP Basic Authentication Scheme) 4. User Provisioning: If you plan to use [Just-In-Time (JIT) User Provisioning](https://www.gooddata.com/docs/cloud/manage-organization/set-up-authentication/#just-in-time-jit-user-provisioning), the "Export users to this App" option is recommended. The knowledge sources don't explicitly confirm successful customer implementations with JumpCloud, but the [general OIDC setup guide](https://www.gooddata.com/docs/cloud/manage-organization/set-up-authentication/) states that GoodData should support all OIDC IdPs that expose the OpenID configuration document at

https://<your_issuer_url>/.well-known/openid-configuration

. ## SAML Authentication Regarding SAML, it is now supported in GoodData Cloud as part of the Enterprise tier. According to the [Federated Identity Management documentation](https://www.gooddata.com/docs/cloud/manage-organization/set-up-authentication/federated-id-management/), you can use [SAML authentication](https://www.gooddata.com/docs/cloud/manage-organization/set-up-authentication/saml-authentication/) and even combine both MOIDC and SAML authentication simultaneously. To set up SAML, you'll need to contact GoodData support to enable the Federated Identity Management feature, and then use the

/api/v1/entities/identityProviders

API endpoint with SAML-specific configuration. I recommend reaching out to GoodData support to discuss your specific use case and get assistance with either the JumpCloud OIDC setup or enabling SAML authentication.

Hello Cian, Thank you for reaching out to us. As you can see, from our AI assistant,, there was a case of another customer, where they tried to use JumpCloud. Also we have some experience with other customers. But, to understand better, can you explain why you can not get it to work? where you see any error, or in which step, also you can share with us your settings (feel free to use DM). Regarding your second question about SAML, I believe this should be discussed with your Account Owner, as it is part of the Enterprise Tier. Please, provide more details about your settings and attempts to use JumpCloud, and we will be happy to assist you.

Hey @Mauricio Cabezas, I followed the advice from the case with the other customer and its still not working (and the case does not have any resolution). I will follow up with a DM of our settings.

Thank you Cian for sharing, rigth now I am looking into this.

And then we need to create the user with the jumpcloud user ID ?

Exactly, you can use this call (just an example):

curl --request POST \
  --header "Authorization: Bearer $API_TOKEN" \
  --header 'Content-Type: application/vnd.gooddata.api+json' \
  --data '{
      "data": {
        "id": "Cian",
        "type": "user",
        "attributes": {
          "authenticationId": "1234XXXXXxxxxx"
        },
        "relationships": {
          "userGroups": {
            "data": [ {
              "id": "adminGroup",
              "type": "userGroup"
            } ]
          }
        }
      }
}' $HOST_URL/api/v1/entities/users

Please, give it a try. In any case, if it fails then, can you please share a traceID if you can see it to check then in our logs.

Hey Mauricio, I tested it but it still didn't work 😞 I'm on vacation for the next two weeks - so have put this on hold until I'm back. But if you have any ideas, please send them here.

Hello, Cian. Thank you for letting us know. We will keep this case on hold on our side while we wait for your update. Enjoy your holidays! 🙂