[ https://issues.apache.org/jira/browse/ARTEMIS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612778#comment-17612778 ]
daves commented on ARTEMIS-4027: -------------------------------- Yes, I would like to build a small web based client to manage Artemis. The current console contains many useful features, but at the same time is very annoying to use. Some problems I have with the current console: * Constant logouts * Collapse/open state of left navigation (black area) not persisted * Too much space wasted on "non-content elements" like the header or the #artemistree * Tables like Queues do not persist items per page, filters and columns to display * Purging or deleting a Queue requires too many clicks and due to the navigation filters on the Queue table get lost * In general...Death by 1000 papercuts My goal is to build a client which contains much less functionality but improve on the UX. I was planing to learn blazor and evaluate it for other applications for a long time...and the idea was to use this project for that purpose. I don't know yet what functionality the client will contain, but I will focus on a life updating Queue overview with easier functions to see subscribers and manage the content of a Queue. > Cannot access management API due to CORS problems (403) > ------------------------------------------------------- > > Key: ARTEMIS-4027 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4027 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: API > Affects Versions: 2.25.0 > Reporter: daves > Priority: Major > Attachments: artemis.log, consoleError.JPG, etc.zip, f1.JPG, f2.JPG, > options.JPG > > > I try to access the management API from a client app running in chrome. > This does not work because the preflight check fails. > OPTIONS request: > > {code:java} > fetch("http://localhost:8161/console/jolokia/?maxDepth=7&maxCollectionSize=50000&ignoreErrors=false&canonicalNaming=false", > { > "headers": { > "accept": "*/*", > "accept-language": "en-US,en;q=0.9", > "sec-fetch-dest": "empty", > "sec-fetch-mode": "cors", > "sec-fetch-site": "cross-site" > }, > "referrerPolicy": "strict-origin-when-cross-origin", > "body": null, > "method": "OPTIONS", > "mode": "cors", > "credentials": "omit" > }); > > {code} > > The request fails with a 403 not authenticated... which is strange since > preflight checks must not be authenticated. > !options.JPG! > > I tried to configure CORS in the jolokia-access.xml file like so: > > > {code:java} > <restrict> > <cors> > <!-- Allow cross origin access from localhost ... --> > <allow-origin>*://*</allow-origin> > <!-- Options from this point on are auto-generated by Create.java from > the Artemis CLI --> > <!-- Check for the proper origin on the server side, too --> > <strict-checking /> > </cors> </restrict>{code} > > > I also tried to specify the URL and port of my application explicitly. But > this did not work either. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)