Skip to main content
Skip table of contents

Keycloak Configurations for APISIX-Proxy Enablement

This document contains all the configurations required for the setup of APISIX-Proxy for API Authentication in CX. Following configurations are the prerequisite before the enablement.

  • First go to your Keycloak instance and login, then go to the expertflow realm.

    Screenshot from 2025-04-10 13-17-06.png
  • Then click on clients option in left panel and then select cim.

    Screenshot from 2025-04-10 13-19-50.png
  • Now, go to the client scopes and click on cim-dedicated under Assigned client scope.

    Screenshot from 2025-04-10 13-20-02.png
  • Click on Add Mapper and then select By configuration.

    Screenshot from 2025-04-10 13-20-12.png
  • Click on Audience.

    Screenshot from 2025-04-10 13-20-20.png
  • Provide Name as “fix-audience”, select cim in Included Client Audience. Check “Add to ID Token” toggle as On and Save.

    Screenshot from 2025-04-10 13-21-00.png

Create a Customer User:

This user is responsible for creation of Access Token for each customer in Customer Widget.

  • Go to the Users tab in left Control Panel.

    Screenshot from 2025-04-10 13-21-09.png
  • Click on Add User and provide username as “customer” and enable Email Verified toggle to On and click save.

    Screenshot from 2025-04-10 13-21-26.png
  • Once user is created, go to Credentials and click on Set Password, provide credentials as customer and toggle temporary to false. Click save

    Screenshot from 2025-04-10 13-21-56.png

  • (Included steps after 4.10.1 onwards) After creating customer, assign it a customer role. Click on the Realm roles and check if the customer role exists. If it exists then skip the creation process, else create a customer role.

    Screenshot from 2025-08-13 16-14-57-1.png

  • Go to the customer user and the click on Role mapping.

    Screenshot from 2025-08-13 16-15-28.png

  • Assign customer role to user along with offline_access and uma_authorization.

    Screenshot from 2025-08-13 16-16-30.png
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.