Hi, I still do not understand what you are trying to achieve - the EmberJS WebUI transforms a JSON based "page description" into a web page with texts, forms and buttons. Any logic is contained in the server backend and can be widely configured from there using the YAML configuration, for any custom requirements it is also possible to write your own perl modules but there is basically nothing you can/should change on the browser side.
The Ember component translates user input into JSON, sends it to the webserver which handles the requests via the script found in server/cgi-bin/webui.fcgi which then calls the modules in core/server/OpenXPKI/Client/UI. The webserver code now talks to the backend using a Unix Socket and API calls and creates a result page from it which is send back to the Ember UI. You can find the reference to this rendering API here https://openxpki.readthedocs.io/en/latest/reference/developer/webui.html Oliver Am 27.04.21 um 09:14 schrieb Node Developer via OpenXPKI-devel: > Dear Developers, > > I have spent several days on finding out the design workflow of > OpenXPKI WebUI that how it interacts with the back-end. It is built in > EmberJS but the code that interacts with back-end is not found to me. > The back-end API is working fine. I want to develop a limited, focused > and customised web interface for the OpenXPKI from scratch. Please > guide me. > > Regards > > On Wednesday, April 14, 2021, 04:53:47 PM GMT+5, Martin Bartosch > <[email protected]> wrote: > > > Hi, > > > > I installed on Debian 10 Buster using the precompiled packages. The > back-end and front-end work fine. I want to customize the publically > available community edition/version 3.10.0 of OpenXPKI. > > > > I have downloaded and inspected the code downloaded from > "https://github.com/openxpki/openxpki/tree/develop/core/htdocs_source > <https://github.com/openxpki/openxpki/tree/develop/core/htdocs_source>" > > > > But I couldn't find the code in front-end UI which > communicates/interacts with the back-end core for database > connectivity and PKI/certificate operations. > > > If I understand you correctly you want to customize OpenXPKI in a way > that it behaves differently, e. g. different certificate profiles or > workflows. > The frontend is not the right place to do that, it only renders the > state of the workflow instance currently handled. > > Best regards, > > Martin > > > > > _______________________________________________ > OpenXPKI-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-devel -- Protect your environment - close windows and adopt a penguin!
_______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
