Issue with IMX Web Portal Customization

[thomas007-smplid]

Is this a regression?

No

Severity

🔴 Critical – blocks key functionality

Please provide the branch(es) you discovered this issue in

v100

Environment Details

Microsoft Edge, Windows server, Version 10.0 LTS

Please provide a minimal set of steps to reproduce the issue

1.Downloaded and extracted the source code (both tag 10.0.0 and branch V100).

2.Opened the project in Visual Studio Code.

3.Navigated to the imxweb folder.

4.Installed dependencies using:
npm install

5.Followed the build steps from the documentation:

npm run build qbm

npm run build qer

npm run start qer-app-portal

6.During the third command (qer-app-portal), I received errors related to dependent projects (see attached screenshot).

7.Based on the GitHub README, I then used Nx to build the application and its dependencies:

npx nx build qer-app-portal

This completed successfully.

8.After that, I deployed the generated files from the dist folder using the following PowerShell commands:

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qer*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qer.zip" -Force

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qbm*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qbm.zip" -Force

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qer-app-portal*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qer-app-portal.zip" -Force

9.Restarted IIS and tested the portal.

10.Issue

After deployment, the portal shows the following error:

"An unexpected server error occurred"

Description

I am currently trying to customize the Identity Manager Web Portal using the official source code from your GitHub repository.

However, I am facing issues even when using the unmodified source code, and I would appreciate your guidance.

Environment

Identity Manager Version: 10.x

Source Code: GitHub (Tag 10.0.0 and Branch V100)

Deployment: IIS / ApiServer

OS: Windows Server

Node.js: Installed as per documentation

Steps Performed

Downloaded and extracted the source code (both tag 10.0.0 and branch V100).

Opened the project in Visual Studio Code.

Navigated to the imxweb folder.

Installed dependencies using:
npm install

Followed the build steps from the documentation:

npm run build qbm

npm run build qer

npm run start qer-app-portal

During the third command (qer-app-portal), I received errors related to dependent projects (see attached screenshot).

Based on the GitHub README, I then used Nx to build the application and its dependencies:

npx nx build qer-app-portal

This completed successfully.

After that, I deployed the generated files from the dist folder using the following PowerShell commands:

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qer*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qer.zip" -Force

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qbm*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qbm.zip" -Force

Compress-Archive -Path "C:\Web Portal Customization\IdentityManager.Imx-100\IdentityManager.Imx-100\imxweb\dist\qer-app-portal*" -DestinationPath "C:\inetpub\wwwroot\ApiServer\bin\imxweb\custom\Html_qer-app-portal.zip" -Force

Restarted IIS and tested the portal.

Issue

After deployment, the portal shows the following error:

"An unexpected server error occurred"

(Please see attached screenshot.)

This happens even when using the original source code without any customization.

I followed the same steps for both:

Tag version 10.0.0

Branch V100

Both resulted in the same issue.

Request for Support

Could you please advise:

Whether my build and deployment steps are correct.

If there are any additional required steps for building and deploying customized portals.

If there are specific environment or configuration prerequisites that I may be missing.

What is the recommended approach to proceed with portal customization in this scenario.

At this stage, I am unable to proceed with customization because the portal fails even with the default source.

Your support and guidance would be highly appreciated.

Thank you for your time and assistance.

Describe what you expected to happen versus what actually happened

I would expect the code to work fine after I moved it to Imxweb\custom
but it gave me error

Relevant logs or console output

Add a screenshot(s) if that helps illustrate the problem

Suggested Fix

No response

Anything else?

No response

Before submitting...

• I have searched for existing issues that match this one on github and on the community support page
• I have included all necessary details to reproduce this issue

[flofiedler]

Note: I'm not part of One Identity or the product team. This is just based on my own understanding and experience.

I think there are two different things getting mixed up here, so it may help to separate them.

1. Local development environment

To set up dependencies and build the app for local development with nx:

npm run nx:build qer-app-portal

To run the project locally:

npm run start qer-app-portal

This setup requires a local API server instance (hosted via imxclient.exe on port 8182). If that API isn’t running, the app will fail during startup and you’ll see the “Application could not be initialized” error. In that case, you should also see failed/unresolved requests in the browser’s network tab.

2. Deployed environment (IIS)

To create a full, deployable build of the web portal with nx:

npm run build:production qer-app-portal

This produces the output that can be zipped and copied to the IIS working directory, as you described.

The important part here is that the production build flag must be used, because the environment is baked in at build time (qer-app-portal/src/environments). Based on the commands you mentioned, it’s likely that IIS is currently hosting a build that was created with a dev configuration and is therefore still trying to connect to localhost.

---

Another thing I'm not sure about is the last PowerShell command. I think there should be a "\" between "qer-app-portal" and the trailing asterisk