- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2017 10:57 AM
Dear community.
For my application on ADF I use Alfres Cocommunity (latest) as the Content Services and Alfresco Process Services 1.5.2x as Process Services.
Alfresco Process Services started on 8080 port,Alfresco Cocommunity started on port 9080.
In my Alfresco ADF app I configure the relevant ports and address.
In the configurationAlfresco Process Services file "activiti-app.proportis"
added
"cors.enabled = true
security.csrf.disabled = true"
When I try to log in Alfresco ADF app I get an error message
"Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc."
How I can fix this ERROR?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 10:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2017 11:20 AM
Can you please confirm you are using the Enterprise version of the Process Services, not the Community one? The Community one won't login in any case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2017 06:48 AM
I using the Enterprise version of the Process Services with an established trial license for 30 days (as in step-by-step induction).
The image shows the software version and the license validity period.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2017 09:55 AM
Is it really only my problem - at the beginning? ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:20 AM
Can you give a look here https://community.alfresco.com/community/application-development-framework/blog/2017/06/20/adf-cors-... ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:23 AM
In fact, I tried all three strategies ... And still there is an error...(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:29 AM
what do you have in the settings page?
Can I see the configuration of your webpack.common.js proxy part?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:50 AM
devServer: { contentBase: helpers.root('dist'), compress: true, port: 3000, historyApiFallback: true, host: '0.0.0.0', inline: true, proxy: { '/ecm': { target: { host: "0.0.0.0", protocol: 'http:', port: 8080 }, pathRewrite: { '^/ecm': '' } }, '/bpm': { target: { host: "0.0.0.0", protocol: 'http:', port: 9999 }, pathRewrite: { '^/bpm': '' } } } },
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 09:02 AM
So from your first screenshot seems that you have the PS in a different domain and port that the one configured in the Proxy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 09:05 AM
devServer: {
contentBase: helpers.root('dist'),
compress: true,
port: 3000,
historyApiFallback: true,
host: '0.0.0.0',
inline: true,
proxy: {
'/ecm': {
target: {
host: "0.0.0.0",
protocol: 'http:',
port: 8080
},
pathRewrite: {
'^/ecm': ''
}
},
'/bpm': {
target: {
host: "192.168.122.238",
protocol: 'http:',
port: 8080
},
pathRewrite: {
'^/bpm': ''
}
}
}
},
should be something like that your conf for Process Service
