This document summarizes a single sign-on user flow for a kiosk and mobile web clock application. It involves multiple layers including a network layer, presentation layer, web services layer, and data layer. The presentation layer is protected by an Oracle WebGate that will send successfully authenticated users to terms and conditions for the web clock application. The user is identified by their 10-digit enterprise ID after translation from their network account by an API web service. The data is accessed from WebLogic application servers through a reverse proxy on Apache web servers.

1. Internet
Network Layer
Presentation Layer
Web Services Layer
F5-External Reverse Proxy
Idmservices.domain.com
Oracle Web Gate
External Login
Login
Is user
authenticated?
Data Layer
F5 Reverse Proxy
Apache Oracle HTTP Server
(OHS)
WebClock.domain.com
Oracle WebGate
Presentation Layer is protected by the
Oracle WebGate. Users seen as guests
to this resource will be sent to Terms &
Conditions with application ID=Wclock
after successful login
The user will be identified with the 10 digit Enterprise ID.
API Web Services processes the translation from network
account (DomainDomain User) to Enterprise ID
The Data Layer is surfaced from the WebLogic Web Servers which
integrates with PeopleSoft Application Servers. The Apache Web Servers
are setup as Reverse Proxy to access the data only through the WebLogic
Web Servers on behalf of the client. These are new PeopleSoft Websites
Oracle
Database
Kiosk
PeopleSoft - WebLogic
Mobile Web Clock User Opens
webclock.domain.com
Kiosk User Opens a desktop link configured
to access Jump URL with Application
ID=”Kiosk”
Terms and Condition
mClock
Kiosk & Mobile User Single Sign-On Flow
Yes No
Federation