CORS Policy Error "No Access-Control-Allow-Origin' header is present" when Acessing Sales Application And Redirecting URL Issue
(Doc ID 2798198.1)
Last updated on MARCH 27, 2023
Applies to:
Siebel CRM - Version 15.0 [IP2015] to 16.19 [IP2016] [Release V15 to V16]Information in this document applies to any platform.
Symptoms
Redirecting URL is not working with Siebel 2016 Sales application with IIS web server and getting CORS policy Error
The issue can be reproduced at will with the following steps:
1. Configured Application Object Mannager (AOM) with SSO enabled with windows authentication.
2. Using url https://hotname.domainname/saleshttps_enu/for logging to application. But it was redirecting to https://hostname/saleshttps_enu/. (without domainname)
3. To overcome this , enabled FQDN in eapps.cfg.
4. But using http://siebeldev01/saleshttps_enu/, it is redirecting to https://sie****dev.domainname/saleshttps_enu/
5. FQDN we have specified as sieb***ev.domainname in eapps.cfg
Changes
After enabling FQDN for redirecting URL to use domain name along with hostname, request is redirected to different URL and seeing CORS policy error.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |