moqui

Running Moqui on Tomcat over SSL (setting http-port and htts-port) - return code 302

风格不统一 提交于 2020-01-17 04:43:05
问题 I have a Tomcat server with SSL configured. I can access the Tomcat Web Application Manager, the connection is secured. Tomcat server is accessible on ports ports 80 and 443, and is dockerized (the container's ports are 8080 and 8443). The application is working fine over http, no problems spotted. Then I decided to switch to https. So I modified the MoquiProductionConf.xml web-app tag this way: <webapp-list> <!-- NOTE: when you set https-enabled="true" make sure to set the http-port and

Search not working (as expected) for list-form PartyListForm - column loaded from mantle.party.PartyIdentification

|▌冷眼眸甩不掉的悲伤 提交于 2020-01-06 21:20:10
问题 I started by using PartyListForm in FindParty.xml. This list loads data related to parties, in my case with Supplier role. I added a new column with an ID from mantle.party.PartyIdentification, with specific partyIdTypeEnumId . The result is satisfactory, I have a list of Suppliers, with their names and respective IDs shown. The problem starts in the moment, when I want to let the user search through those IDs. It does not work. This is the definition of the column: <field name="idValue">

Adding a second webapp

对着背影说爱祢 提交于 2019-12-25 04:52:10
问题 I am struggling to setup a public website in Moqui, I am trying to have (dev-)www.example.net as the public marketing site and signup forms. Then the tennants on [tennant-name].example.net I have setup a basic component and then edited MoquiDevConf.xml, modified the webapp-list as shown below: <webapp-list> <webapp name="webpublic" http-port="8080" https-enabled="false"> <root-screen host="dev-www.example.net" location="component://webpublic/screen/webpublic.xml"/> </webapp> <webapp name=

Moqui deployment to AWS on Elastic Beanstalk Tomcat instance

血红的双手。 提交于 2019-12-20 06:47:11
问题 Background We have been running Moqui 2.0 with the embedded Jetty server on Elastic Beanstalk using a Java environment for about a year now. For security reasons, we had the application running in a private subnet along with the Postgres database and accessing it over VPN. Because of this, we never bothered to enable HTTPS access. We now want to deploy Moqui in the public subnet so that it can be accessed without the VPN and therefore we need HTTPS access. Sidenote: Bear in mind, I have

Does Moqui framework 2.0 Still support Mutli-tenency

无人久伴 提交于 2019-12-11 06:50:58
问题 I would like to use the Moqui framework 2.0 for next project which should be SaaS based model.Multi-tenent(Seperate database for each client). Please confirm does it still support Multi-tenency. So that i will kick off my project implmentation with Moqui framework 2.0 next genertion Entprise framwork. Thanks in advance. Nyamath ullakhan 回答1: The old multi-tenant functionality in Moqui Framework has been deprecated in 2.0.0 by the multi-instance features. The general idea is that instead of

Rest API call with api_key in header fails if nginx is proxying moqui application

為{幸葍}努か 提交于 2019-12-11 04:14:16
问题 When run moqui on 8080 port, and access it directly by api curl -X GET -H "api_key: {apiKey}" http://localhost:8080/rest/s1/example/examples/TEST2 it returns json result of example TEST2. But when nginx is put in front of mqoui application. proxy to http://localhost:8080, then the api access fails with 403 { "errorCode": 403, "errors": "User null is not authorized for View on REST Path /example/examples/{exampleId}\nCurrent artifact info: [name:'/example/examples/{exampleId}', type:'AT_REST

How to create a publicly accessible REST API in Moqui

ぐ巨炮叔叔 提交于 2019-12-08 13:16:52
问题 What is the best way to create a publicly accessible REST API in Moqui? By public I mean an API that does not require prior authentication. The only work around I found so far was to create a user "public_api" and grant him access to the desired services. The client applications then use this user to authenticate with the Moqui server. 回答1: There is now an update in moqui-framework commit #44272ba to support the require-authentication element on the Service REST API resource, id, and method