---
title: "SSL certificates"
canonical: "https://docs.cuesystem.com/space/Dep/151322658/SSL%20certificates"
format: markdown
---
You need to create **validated** certificates signed by a trusted certification authority for those web domains mentioned in the previous chapter.

In some cases, it is possible to use **self-signed** certificates, but for reasons of low security, this is **not recommended** and in some cases **not even possible**. When using self-signed certificates, you will need to **manually allow access** to these pages in your browser, because self-signed domains are not considered trusted. Signing with self-signed certificates is done by the Cue Control Panel and **no user action is required**.

> ⚠️ **Self-signed certificates cannot be used for CUE Assist**, which is part of **CUE Solution version 6 and higher**, in **Microsoft 365** and **Google Workspace** environments.  
> ⚠️ This is because OAuth 2.0 Authorization Code Flow is used for authorization in these cases and the use of self-signed certificates is prohibited here.

![image](media://bc17cbc5-a8f7-48b3-85d3-1f67ccda29ee)

> ℹ️ The certificates of all domains used must be trusted by the server running the API. If they are self-signed certificates (or certificates signed by a company certification authority), they must be added as trusted root CAs for the entire server. For technical reasons, the server must perceive these certificates as completely valid and trusted.

> Macro (excerpt-include)




> ℹ️ You can find more about creating certificates [here](https://cue.atlassian.net/wiki/spaces/HTBCA/pages/465534996).