A common problem experienced after successfully setting up SSO is the realization that the cluster that was just created no longer has a login page for you to access the Sourcing application as the Enterprise user. This is because the hostname of the cluster is now only accepting basic authentication which doesn’t present a login prompt. There is one address that should always be accessible to those with machine or adequate permission within the network that being the IP address. The default cluster that contains allows the system user access will always present a functioning login screen when it’s reached, that’s why we need to take advantage of this to allow Enterprise to login through the same location.
You should have a cluster created that housed your non-SSO configuration before you created an SSO cluster. This needs to be enabled, and have a directory associated with it that is either set to the LDAP or Local type authentication depending on who else you want apart from Enterprise using this login page. Within the Cluster the hostname field needs to be updated to a value that is different from that stored in the SSO cluster, something like the non-qualified hostname or a junk string, and the alias field needs to be updated to contain the IP address.
You may have some issues reactivating the non-SSO cluster as it may have been deactivated during the setting up of SSO. In order to reactivate a cluster it requires 2 things; association with a Context and with a Directory. Association with a directory is easy enough, however I know there was some concern about switching the associations of the cluster from the SSO to non-SSO, and I can assure you that the switch only needs to occur in order to re-activate the non SSO cluster unchecking the inactive radio button.
Now when you access the Default/System cluster there will be a directory associated with the internal buyside login area. This should allow you to login with enterprise and whatever users are associated with that directory. It’s worth keeping in mind that users assigned to this directory can only login via this page and SSO won’t work for them, making it best left for Administrative tasks.
This process has been overhauled and is far easier in SAP Sourcing 7.
