I am suddenly facing access issues regarding app access at my corporate company. I get an error message that system resources will not load when trying to access the login page of my site. It was working fine for many months and login still works fine externally. I am told the internal IT need a certificate. I followed the link to complete the details about the site but am faced with this question:
Certificate Signing Request (CSR)
NOTE: Requester must provide a valid CSR with the required CN(Common Name) and Respective SANs (Subject Alternative Names ). You must generate the CSR from your application server or from any CSR generation Utility like: Digicert (KB5003078) or Using Microsoft Certificate Management Console.
Can anyone advise how I can provide this information for my Glide page? I note that I am not using any URL redirects.
Hey Simon, Glide doesn’t issue or accept custom SSL certificates or CSRs,all Glide apps are automatically secured with HTTPS under Glide’s own managed certificate. So there’s no way (or need) to generate a CSR from your side.
If your IT team is asking for one, that usually applies to internally hosted or self-managed systems. In this case, they just need to know that your Glide app is hosted externally and already protected by Glide’s SSL.
If your app uses a custom domain, Glide automatically handles the SSL setup for that domain too. You can reach out to Glide Support to confirm the certificate details if your IT team needs verification.
I’ve seen this before with corporate networks, once IT understands that the certificate is managed by Glide, access usually gets sorted quick.
Thanks this is super helpful. Just one question, I modified the URL for the page proposed by Glide - but I did not set up a URL redirect. Can I assume this counts as the Glide certificate? Ie. In this case, they just need to know that the Glide app is hosted externally and already protected by Glide’s SSL?
Exactly , as long as the app is hosted through Glide (even if you modified the URL they provided), it’s still covered under Glide’s SSL certificate. There’s no extra setup or redirect needed on your side.
So you can confirm to your IT team that the site is already HTTPS-secured by Glide, they just need to allow it through their system