New User Registration Context
A New User Registration context is optionally used when the New User Registration framework is consumed by a specific self-service online transaction. A New User Registration context is defined through a New User Registration context ID. The context ID is an optional element. You embed the context ID in a URL that is used to transfer a user to the New User Registration login page. You need a New User Registration context ID if you want to seamlessly assign application-specific security roles to the newly authenticated user, and then transfer the user to the target page for the self-service online transaction that the user wants to access. The Gatekeeper uses the Context ID that you include in the URL to grant the user the required security roles, and to access the target page.
The New User Registration Context ID is read by the Gatekeeper immediately after a user is successfully authenticated into your system. The New User Registration Context ID defines the security roles that the system should assign to the user. This ensures that the user has the required security roles to be automatically transferred to the target page for that specific self-service transaction and perform the online transaction. Both security provisioning and page transfer occur after a guest or returning user is successfully authenticated by New User Registration into your system. You can define a New User Registration Context for each online self-service transaction that you integrate with New User Registration. Each transaction has its own security provisioned and target page information.
To define a New User Registration Context, use the New User Registration Context page (SCC_APPL_CONTEXT). The security provisioning is defined by roles and the target page can either be a PeopleSoft Internet Architecture (PIA) page defined in your PeopleSoft system or a URL to an external site. Provisioning security or transferring to a target page is optional. Create a New User Registration Context for your integrated self-service transaction only if you want to provision specific security for the transaction or to transfer the user directly to a target page related to the self-service transaction.
You can create a default New User Registration Context ID. If there is no New User Registration Context ID in the URL when a user accesses the New User Registration login page, the default context ID is used to provision security or transfer the user to a target page. In this case, you should set up your default context ID to contain generic information such as your institution’s home page, which is then used as the target page.
See: