<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Installed apps on Quollix</title><link>https://quollix.org/docs/usage/installed-apps/</link><description>Recent content in Installed apps on Quollix</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://quollix.org/docs/usage/installed-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>Forgejo</title><link>https://quollix.org/docs/usage/installed-apps/forgejo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/installed-apps/forgejo/</guid><description>&lt;p&gt;A general rule in Forgejo is that many settings cannot be changed via the web GUI once the installation wizard is completed. However, you can still modify them by directly editing the &lt;code&gt;app.ini&lt;/code&gt; file inside the container as described below. As this is a somewhat hacky solution, we recommend deciding whether to allow self-registration before deploying a production instance.&lt;/p&gt;
&lt;h3 id="installation-wizard"&gt;Installation Wizard&lt;/h3&gt;
&lt;p&gt;When visiting the Forgejo web UI for the first time:&lt;/p&gt;</description></item><item><title>Jitsi</title><link>https://quollix.org/docs/usage/installed-apps/jitsi/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/installed-apps/jitsi/</guid><description>&lt;p&gt;By default, Jitsi does not enforce authentication and allows anyone with access to the web interface to create and join meetings.
Access is managed through Quollix’s access policies. The following access policies are available:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Public: Anyone with access to the Jitsi web interface can create and join meetings. No authentication is required.&lt;/li&gt;
&lt;li&gt;Authenticated / Group restricted: Anonymous users have no access and cannot create or join meetings. Access is limited to authenticated users / to users who are members of specific groups that are allowed to use the Jitsi app.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Odoo</title><link>https://quollix.org/docs/usage/installed-apps/archive/odoo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/usage/installed-apps/archive/odoo/</guid><description>&lt;h3 id="setup"&gt;Setup&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;At first visit, write down or save the master password presented.&lt;/li&gt;
&lt;li&gt;Set Database: &lt;code&gt;odoo&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Enter email and password, which are the future login credentials for the admin account&lt;/li&gt;
&lt;li&gt;Click &amp;ldquo;Create database&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Login with the just set credentials&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="single-sign-on--oidc"&gt;Single-Sign On / OIDC&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Odoo icon &amp;gt; Settings &amp;gt; Integrations
&lt;ul&gt;
&lt;li&gt;enable &amp;lsquo;OAuth Authentication&amp;rsquo; &amp;gt; Save&lt;/li&gt;
&lt;li&gt;You will be logged out. Login and go to the same page again.&lt;/li&gt;
&lt;li&gt;OAuthAuthentication &amp;gt; OAuth Providers:
&lt;ul&gt;
&lt;li&gt;Delete existing proiders&lt;/li&gt;
&lt;li&gt;New &amp;gt; Provider:
&lt;ul&gt;
&lt;li&gt;Provider Name: Quollix&lt;/li&gt;
&lt;li&gt;Client ID: &lt;code&gt;enter client ID from OIDC page&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Allowed: enable&lt;/li&gt;
&lt;li&gt;Login button label: &amp;ldquo;Login with Quollix&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Authorization URL: &lt;code&gt;https://quollix.&amp;lt;server-host&amp;gt;/api/authorize&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Scope: &lt;code&gt;openid profile email&lt;/code&gt; (leave default)&lt;/li&gt;
&lt;li&gt;UserInfo URL: &lt;code&gt;https://quollix.&amp;lt;server-host&amp;gt;/api/userinfo&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;!-- it seems that only public auth flow is possible this way --&gt;</description></item></channel></rss>