One Identity open source projects are supported through One Identity GitHub issues and the One Identity Community. This includes all scripts, plugins, SDKs, modules, code snippets or other solutions. For assistance with any One Identity GitHub project, please raise a new Issue on the One Identity GitHub project page. You may also visit the One Identity Community to ask questions. Requests for assistance made through official One Identity Support will be referred back to GitHub and the One Identity Community forums where those requests can benefit all users.

• The repository has been updated with the source code for the Identity Manager 9.0 release in the v90 branch.
• The build now supports case-sensitive file systems (namely Linux) in the v90 branch.

• Added clarification on the branches.
• The v82 branch has been updated with the contents of the 8.2.1 rollup package.
• The build definition has been split into separate steps for each package.

The repository has been updated with the code changes for the Identity Manager 8.2.1 release.

This repository contains the source code for the HTML5 applications contained in Identity Manager.

It is a monorepo containing the Angular workspace, which consists of apps and libraries.

By forking this repository, you may create customized versions of the projects and add them to your Identity Manager deployment.

Each Angular library and app belongs to a folder in the projects directory. The workspace is defined in the angular.json file.

Each Angular library belongs to the Identity Manager module of the same name.

A (non-plugin) library acts like a regular compile-time dependency. A plugin library is loaded dynamically at runtime, as determined by the plugins' imx-plugin-config.json files.

For more information about each project, see the readme.md files in each project's folder.

To install the required dependencies, run npm install in the root folder of the workspace.

To build any library or app, run npm build <name>. Note that you must build each library in the correct order; along with any plugins that you want to include. For example, to build qer-app-portal, you need to build at least the following in this order:

• qbm
• qer
• qer-app-portal

When changing the code of a library, you will need to build and deploy customized versions of all the apps that should use the customized versions. For example, changing qer will require that you also compile qer-app-portal, qer-app-operationssupport and qer-app-pwdportal because all of these apps include qbm.

When changing the code of a plugin library, you will need to build and deploy customized versions of the plugin library itself, and all plugin libraries depending on it. For example, changing tsb will require that you also compile aad and o3t because these plugins include tsb.

Note: Starling CertAccess currently does not support hosting custom HTML5 apps.

Running and debugging web applications is possible using the default tools of the Angular CLI toolchain. For example, you can use ng serve qer-app-portal to debug the Portal app.

You will need an API Server instance that the web applications will connect to. You can host an API Server locally for development purposes. Run the following command on the command line:

imxclient.exe run-apiserver -B

The web apps will connect to the API Server using the URL defined in the application's environment.ts file. The default setting is http:https://localhost:8182 which is the default URL that a local API Server will run on.

Please refer to the HTML Development Guide for step-by-step instructions on getting started.

The following table shows the branches in this repository corresponding to each product version.

We plan to push updates for each minor and major product release, allowing developers to track source code changes from one version to the next. Occasionally we may also publish important bug fixes.

We welcome and appreciate contributions. Here's how you can open a pull request to submit code changes.

1. Fork the project
2. Create your feature branch (git checkout -b feature/AmazingFeature)
3. Commit your changes (git commit -m 'Add some AmazingFeature')
4. Push to the branch (git push origin feature/AmazingFeature)
5. Open a pull request

Distributed under the One Identity - Open Source License. See LICENSE for more information.