Open lohrm-stabl opened 1 year ago
Hi @lohrm-stabl, that makes sense. There may be a workaround here https://community.getgrist.com/t/azure-ad-saml-sso-and-grist/1269/3
A pull request to allow the entity_id to be overridden would be very welcome :pray:
Hi @lohrm-stabl, that makes sense. There may be a workaround here community.getgrist.com/t/azure-ad-saml-sso-and-grist/1269/3
I have found this as well. At first, I didn't get it working because I Azure AD wouldn't let me customize the entity_id. But by recreating the application, I got it working.
grist.test.xyz
)
GRIST_SAML_IDP_LOGIN
: set to the Login URL provided by AzureGRIST_SAML_IDP_LOGOUT
: set to the Logout URL provided by AzureGRIST_SAML_SP_HOST
: https://grist.test.xyzGRIST_SAML_IDP_CERTS
: download from SAML Certificates > Certificate (Base64), upload to your server and put file path hereGRIST_SAML_SP_CERT
: will be set laterGRIST_SAML_SP_KEY
: will be set laterGRIST_SAML_IDP_UNENCRYPTED
: set to 1
openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365
(adjust days as needed)openssl pkcs12 -export -out certificate.pfx -inkey key.pem -in cert.pem
GRIST_SAML_SP_CERT
and GRIST_SAML_SP_KEY
to the public and private certificate key files you just generated
Currently, Grist cannot be used with AzureAD.
The error one gets with
GRIST_SAML_SP_HOST = https://grist.mydomain
is:The issue probably originates from this line: https://github.com/gristlabs/grist-core/blob/main/app/server/lib/SamlConfig.ts#L85 The GRIST_SAML_SP_HOST is used as part of the
entity_id
. This should be a separate variable so one can set it to the actual client id.