Last updated on MARCH 02, 2017
Applies to:Siebel System Software - Version 7.5.3  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 
Database: Oracle 9i
*** Checked for relevancy 27-Feb-2013 ***
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1211032391.
***Checked for relevance on 09-Mar-2011***
Although the questions below refer to "new user registration" in general, we are most interested in the piece that collects applications from prospective partners.
The OOB workflows for new user registration, for example as launched from the PRM Portal application, appear to require LDAP and only LDAP; but there really isn't much documentation on the subject. Can you confirm this? If one implemented SSO, would these workflows work?
Is the workflow which gets invoked when the user presses the "New User" button, for example in the PRM Portal application, configurable or is it dictated by the "FrameEventMethodRegisterNewUser" method? If one were to create a new workflow, would one also need to create a custom control to invoke it?
Back to SSO. we have SSO implementation using Netegrity. Can the Siebel OOB mechanism -- where the app, upon launching, opens in a public mode (i.e. no authentication required/limited views) and after the user provides credentials from the home page & is authenticated, they have access to the full application (the public and protected views of the app) -- function in an SSO environment? It seems that if an application is protected by SSO, the entire application must be protected and there can be no public portion of the application, correct?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms