Hello,
does anybody has a working sample for allowing CORS for the PASOE 11.7 oemanager webapp?
I have tried adding a CORS filter to the config (either anonymous or basic) - but then the setup turned into form based auth ... :-(
I'm intending to call into the oemanager from an Angular 2 application, so cally would for now be from localhost:4200
When I build the angular 2 application and run it from a PASOE static folder, the oemanager access works find.
Thanks!
Mike
Mike,
We have tried to configure the CORS filter for oemanager but it did not work either. So I would have to ask you to log a bug through TechSupport or I can do that for you.
If we figure out any workaround by then, will let you know.
Update from Progress Community
Irfan Mike,
We have tried to configure the CORS filter for oemanager but it did not work either. So I would have to ask you to log a bug through TechSupport or I can do that for you.
If we figure out any workaround by then, will let you know.
You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here.
Flag this post as spam/abuse.
Thank you Mike.
BTW, what was the use-case for you to access oemanager from your client Application. What was the information that you were looking for ?
It's part of the tooling we offer to our developers in our Angular client. An overview of the agents/sessions with the ability to trim them to get new application code loaded.
I will log a bug from case 00404295
Have you/do you need to register the CORS filter in the web.xml e.g.
<filter>
<filter-name>CorsFilter</filter-name>
<filter-class>com.progress.appserv.services.security.OECORSFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>CorsFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
You have to add that in the oemgr<>.xml file. But when we add the CORS filter and the bean definition, it is not picking up those values. So, its a bug.