Hi, i have technical question - i do not exactly u...
# gooddata-platform
j
Hi, i have technical question - i do not exactly understand the error message and therefore can not identify, what is wrong, when trying to log in using PGP SSO:
Copy code
{
  "error": {
    "errorClass": "Error",
    "trace": "",
    "message": "Host part of serverURL must be specified, you might have omitted protocol part.",
    "component": "Webapp",
    "errorId": "a4d3fed0-56fd-4a9b-9404-4ed6a0e5844a",
    "errorCode": "gdc007",
    "parameters": []
  }
}
POST <https://omnetic-dev.on.gooddata.com/gdc/account/customerlogin>
Copy code
{
  "pgpLoginRequest": {
    "encryptedClaims": "-----BEGIN PGP MESSAGE-----\n\n<REDACTED>-----END PGP MESSAGE-----",
    "ssoProvider": "dms_tenant_gooddata",
    "targetUrl": "/dashboards/embedded"
  }
}
1
j
Hello Jan, One note here before I answer your question - you have just posted your encrypted claims publicly which is really not ideal from the security point of view. I would definitely recommend you to redact it.
j
hi, i believe there is nothing sensitive, thanks for the hint though, i will edit it
👍 1
j
Thank you! Speaking about the error, the root cause are the underscores in the name of your SSO provider - “dms_tenant_gooddata”. The
getHost()
method for URI with underscores/special characters returns null. The SSO provider name must be lowercase and can contain only letters, numbers, dots, and dashes as it is highlighted in our documentation: https://help.gooddata.com/doc/enterprise/en/expand-your-gooddata-platform/gooddata-in[…]t-up-user-authentication-and-sso/gooddata-pgp-single-sign-on
j
ahh damn, i believe that the sso provider with such name should not be even possible to be created in that case 😉
thank you for answering, we will adapt our naming convention
j
Fair point. Thank you for this feedback. I am going to share it with our product team.
🙏 1
p
🎉 New note created.
🙌 1