Despite Specifying FQDN Using OUI_HOSTNAME, Installer Configures Single Sign-On URLs With Hostname Only
(Doc ID 473639.1)
Last updated on AUGUST 16, 2023
Applies to:
Oracle Fusion Middleware - Version 10.1.2.0.2 to 10.1.4.0.1 [Release AS10gR2]Oracle Application Server Single Sign-On - Version 10.1.2.0.2 to 10.1.4.0.1 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
Oracle Application Server Single Sign-On - Version: 10.1.2.0.2 to 10.1.4.0.1
This problem can occur on any platform.
Symptoms
After successfully installing OracleAS 10g Rel 2 Identity Management or Oracle Identity Management 10.1.4.0.1, the Single Sign-On URLs unexpectedly feature only the hostname - rather than the fully qualified hostname.
For example:
Login to Single Sign-On via a partner application such as Oracle Portal.
The login works fine but the url returned by Single Sign-On only features the hostname
Changes
At install time the OUI_HOSTNAME parameter was specified e.g
runInstaller OUI_HOSTNAME=host.domain
or
setup.exe OUI_HOSTNAME=host.domain
This was done after reading this advice given in the Installation Guide
If you are installing OracleAS Single Sign-On, and your hosts file contains only the hostname of your computer, without the domain name, then you will only be able to sign on to the Single Sign-On server using the hostname by itself (without the domain name).
If you want to require a domain name when connecting to the Single Sign-On server, you can edit the hosts file to include the domain name. If you do not want to edit the file, you can use the OUI_HOSTNAME command-line parameter to the installer to override the value in hosts. For example:
prompt> mount_point/1012disk1/runInstaller OUI_HOSTNAME=host.domain
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 |
| References |