Closed calleggr closed 4 years ago
Are you referring to the context of where enduser is located or the context of where IDM is related? That file you are referencing controls where IDM serves the enduser project. You would still need to replace the existing enduser folder contents with a newly generated content (from this project) if you wanted to make use of the IDM hosted UI.
Let me know if that helps at all, if not could you provide some steps for what you are trying to achieve?
We are trying to change the context of the end user UI to "/profile". We are following the steps from this repo to build the end-user UI and replace the enduser folder contents. When we restart openidm the end-user UI does not load and if you check the network trace there are 404 errors for a bunch of JS files called "chunks"
Thanks, Greg
Looks like in the vue.config.js file the publicPath: './',
property got removed. If you add that line in you should be able to build deployable copies to any IDM context. I will put up a PR on our side to add this back in.
Example:
module.exports = { publicPath: './', runtimeCompiler: true, pages: {
Thank you!
Fix merged https://github.com/ForgeRock/end-user-ui/commit/87186e126daeb3f4c503a867ddfe1a3095ee9b28 (sorry PR requests go through our stash and are mirrored out to github after merge).
When using this to customize the end-user-ui for IDM, changing the context in project-dir/conf/ui.context-enduser.json does not work