<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>openid-connect on</title><link>https://docs.whmcs.com/9-1/tags/openid-connect/</link><description>Recent content in openid-connect on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://docs.whmcs.com/9-1/tags/openid-connect/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenID Connect</title><link>https://docs.whmcs.com/9-1/system/authentication/openid-connect/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/system/authentication/openid-connect/</guid><description>Covers generating and resetting OAuth Client API Credentials and authorized redirect URIs at Utilities &amp;gt; System &amp;gt; OpenID Connect, and gives the full step-by-step setup to let cPanel &amp;amp; WHM users log in via WHMCS External Authentication, including the Well Known Config URI and SSL requirements.</description></item><item><title>OpenID Connect Development</title><link>https://docs.whmcs.com/9-1/system/authentication/openid-connect-development/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/system/authentication/openid-connect-development/</guid><description>Documents the developer workflow for OpenID Connect authentication against WHMCS: the .htaccess rewrite rule for the discovery document, the client_id/response_type/scope/redirect_uri/state authentication request parameters, exchanging the authorization code for access_token and id_token, and the iss/sub/aud/iat/exp ID token claims.</description></item><item><title>Certificate Not Detected Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-ssl/certificate-not-detected-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-ssl/certificate-not-detected-errors/</guid><description>Documents the &amp;ldquo;A Certificate Authority verified SSL certificate was not detected&amp;rdquo; warning caused by a misconfigured SSL certificate, with the fix of installing the correct intermediate CA bundle alongside the certificate.</description></item></channel></rss>