POST
|
Hi Everyone, I tried configuring a proxy using the PortalAdmin API by setting {"WebContextURL": "<url string>"}. The update failed, so i thought nothing more of it, until portal stopped working almost immediately. It failed, and now Portal starts, but i get a HTTP 404 when trying to navigate to the home folder. It can see through console, that the HTTP404 is produced by the /sharing/.... request that happens. The only HTML page i can now get up is the PortalAdmin login, and even my Admin username and password is giving me an error message "You are not authorized to use this resource". So now, i cannot go into the Portal admin to change any settings, and i cannot go to Portal as a normal user to do anything! I saw in one file in portal/framework/etc/portal-config.properties that the url i used to change the WebContextURL setting. I reverted this back, restarted Portal and it is still not working!! Is there some config placed into Postgres that i can get at to fix this? I ahve spent half a day trying to resolve this - I have looked in every location & file that has been modified, and nothing is jumping out at me. Many Thanks, Steve
... View more
08-19-2015
09:58 AM
|
0
|
16
|
11174
|
POST
|
Hi Jeff, thank you for replying, that is really useful to know. Actually, the issue was to do with some inheritance crazy-ness going on with IIS. However, it seems, that using web app builder, I am getting a 401 immediately - it is not even prompting for a username/password. I feel like i am close, just not close enough!! If anyone has any experience of CORS on web-tier secure services using Web App builder, I would appreciate. Thanks, Steve
... View more
08-14-2015
08:14 AM
|
0
|
1
|
1947
|
POST
|
Hi Everyone! I have a situation where my application will be required to access web-tiered services across different domains. I have added the following to the web config of web adapter: <customHeaders> <add name="Access-Control-Allow-Credentials" value="true" /> <add name="Access-Control-Allow-Origin" value="http://sub.domain.com" /> </customHeaders> However, when testing in chrome, I receive the following error in console: XMLHttpRequest cannot load <url to secured service>. the Access-Control-Allow-Origin header contains multiple values 'http://sub.domain.com,http://sub.domain.com' .http://sub.domain.com is therefore not allowed access. I have checked everything, i have definitly only configured one header in the web.config. I am using the testing tool available on the enable cors site. Against an unsecured sevrice, it works fine as we don't have to set the allow credentials header, but with secured services, it is not working. Have also tried firefox, and i do not have IE available in this environment. Thanks for anyone who can help! Steve
... View more
08-13-2015
08:14 AM
|
0
|
14
|
10833
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|