Recent Searches

No recent searches

    Popular Articles

      Articles

      View all

        Topics

        View all

          Tickets

          View all
            no results

            Sorry! nothing found for

            What changes for you when we switch qwikinow.de to ariadne.cloud

            Modified on Wed, 14 Oct at 4:56 PM

            After the switch, you reach Ariadne at a new address, for example company.ariadne.cloud instead of company.qwikinow.de. With a few simple steps, your company login, user synchronization, scripts and AI tools keep running without interruption.


            Good to know: In the browser, you don't need to do anything: the old address redirects automatically, so bookmarks and links in emails keep working.


            Some systems don't follow the redirect for security reasons. For those, enter the new address.

            Important: For this switch, you need the support of your IT team. It's best to talk to them now, because some changes must be made before the switch date on 22 October 2026.

            What do you need to do for each access method?

            Access methodWhat to doWhen?Who?
            Browser, bookmarks, links in emailsNothing, the redirect is enough.Nothing to do–
            API clients (scripts, Power BI, integrations)Change the base URL, the API token stays valid.On 22 Oct 2026Whoever maintains the integration
            MCP connectors (ChatGPT, Claude, Copilot Studio)Change the MCP server URL, then re-authorize via OAuth for each user.On 22 Oct 2026Admin of the AI tool, then each user
            EITHER  You use OIDC and SCIM
            OIDC SSO (Entra ID, Okta)Add the new Redirect URI in addition.
            https://<company>.ariadne.cloud/bin/login            		Before 22 Oct 2026Your IT team
            SCIM provisioningChange the Tenant URL, re-enter the Secret Token, run Test Connection.On 22 Oct 2026
            within a few days at the latest            		Your IT team
            OR  You use SAML
            SAML SSO (Entra ID, ADFS, Google Workspace)Add the new Reply URL (ACS URL) in addition, keep the old one for now. Leave the Identifier (Entity ID) and certificate unchanged.Before 22 Oct 2026Your IT team

            Prepare your company login (SAML/OIDC) before the switch date

            Company login

            SAML SSO and OIDC SSO

            Before 22 Oct 2026

            Add the new address now, in addition to the old one. Nothing changes until the switch, and your company login keeps working seamlessly afterwards.

            How to proceed

            • For SAML, add the new Reply URL (ACS URL) in addition to the old one.
            • For OIDC, add the new Redirect URI in addition to the old one: https://<company>.ariadne.cloud/bin/login
            • In Entra ID, you find the SAML Reply URL under Basic SAML Configuration. Enter https://<company>.ariadne.cloud/saml/sp/consume there and mark it as default.
            • Remove the old address only after the switch has worked.
            • The certificate stays the same. You don't need to download or replace anything.
            Warning: Do not change the Identifier (Entity ID), even if it still contains qwikinow.de. Ariadne still expects exactly the value that is entered.
            Important: If you don't add the new address in time, the company login fails after the switch. The redirect doesn't help in this case.

            Adjust user synchronization (SCIM) on the switch date

            User synchronization

            SCIM provisioning

            On 22 Oct 2026

            This way, new employees keep being created automatically and departed employees keep being deactivated. Switch the synchronization on the switch date, within a few days at the latest.

            How to proceed

            • Change the Tenant URL to the new address.
            • Re-enter the Secret Token.
            • Click Test Connection to check the connection.
            • You don't need to resynchronize all users afterwards.
            Important: If you don't make the change, synchronization fails. New employees are then not created and departed employees are not deactivated. Entra keeps retrying for a while and stops the synchronization completely after several weeks of errors.

            Keep scripts, Power BI and integrations running

            API clients

            Scripts, Power BI, integrations

            On 22 Oct 2026

            You only need to adjust the base URL. Your API token stays valid, so you don't need to create a new one.

            What happens if you don't adjust the address

            • Power BI doesn't follow the redirect at all. Scheduled refreshes fail until the address is adjusted.
            • Other programs follow the redirect but lose the access token along the way and report “not authorized”.
            Good to know: “Not authorized” looks like a broken token, but it is only caused by the old address. The token itself stays valid.

            Reconnect your AI tools (MCP) after the switch

            MCP connectors

            ChatGPT, Claude, Copilot Studio

            On 22 Oct 2026

            So your teams can keep using their AI tools with Ariadne knowledge: the admin changes the address, and each user reconnects once.

            How to proceed

            • The admin of the AI tool changes the MCP server URL to the new address.
            • Afterwards, each user re-authorizes once (OAuth re-authorization).
            Important: If you don't make the change, the AI tool reports “Login failed”.

            Related articles

            Was this article helpful?

            That’s Great!

            Thank you for your feedback

            Sorry! We couldn't be helpful

            Thank you for your feedback

            Let us know how can we improve this article!

            Select at least one of the reasons
            CAPTCHA verification is required.

            Feedback sent

            We appreciate your effort and will try to fix the article

            Preview
            0 of 0