Oracle B2C Service Cloud
Formerly know as Oracle Service Cloud and RightNow
Oracle B2C Service customers must set the configuration setting OIT_CORS_ALLOWLIST* properly to ensure the Inlays are approved to interact with your site. Search for the OIT_CORS_ALLOWLIST configuration key. *In versions prior to 20D, this configuration is OIT_CORS_WHITELIST.
Error Access to XMLHttpRequest at ‘https://sample-opa.custhelp.com/web-determinations/redirectQuery’ from origin ‘https://sample.custhelp.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Solution In order to allow only certain websites to embed an Intelligent Advisor interview or flow, you need to set up a cross origin request from the server hosting the application. […]
Endpoint: https://customer.custhelp.com/services/rest/connect/v1.4/incidents/{Incident ID}/threads/ Verb: Post Body:
[HTMLROOT] => /vhosts/site_name[ASSETS_ROOT] => /euf/assets/
Submit SR to Oracle to enable the hidden config verbs. For Agents AGENT_SAML20_SSO_ENABLED SSO_ENABLE_EXTERNAL_IDP For Contacts CONTACT_SAML20_SSO_ENABLED Add the cert thumbprint as plain text (no colons) to the SAML_20_SIGN_CERTS config verb. Assertion Consumer Service (ACS) url https://interface-name.custhelp.com/ci/openlogin/saml/<login> Example: contact.login or contact.emails.address https://interface-name.com/ci/openlogin/saml/subject/contact.emails.address https://interface-name.custhelp.com/ci/openlogin/saml/subject/contact.login Reference Links https://blogs.oracle.com/blogbypuneeth/post/steps-to-configure-saml-20-with-idcs-identity-cloud-service-as-identity-provider-and-jcs-oracle-java-cloud-service-as-service-provider https://videohub.oracle.com/media/Best+Practices+for+Implementing+OSvC+SSO/1_z6r5f5mi http://documentation.custhelp.com/euf/assets/devdocs/cloud22a/olh/CoreFeatures/topicrefs/c_crm_admin_saml_sso.html