1. Key Highlights of ABC’s Proposal
ABCDE’S
OBJECTIVES
ABCDE is seeking strategic partner to implement Single-Sign on (SSO) for ABCDE Customers on External Web
SSO Integration with LMS and Jive
OIM and OAM Integration with
Oracle Internet Directory
OIM configuration for role and entitlements
management
PROPOSAL HIGHLIGHTS
• Migration of all external user profiles from AD to OID
and establishment of a sync
• Provisioning/De-provisioning user access to following
applications using Oracle Identity Manager – SAP ECC
• Implementation of Single Sign On functionality for the
following Web Applications- LMS, JIVE
• Federated SSO for LMS using SAML 2.0 using Oracle
Access Manager
• Role based access provisioning for external users
SOLUTION
• Total engagement duration of 19
weeks including warranty support
for Phase 1
• Customer Go Live at the end of
Week 17 which is inline with
ABCDE’s expectations
TIMELINES
• Deployment of resources from
current ABCDE engagements to
ensure rapid onboarding
• Key resource profiles identified
and ready to start
• Additional resourcing
requirements can be fulfilled
utilizing ABC’s strong talent
across technologies in scope
RESOURCING
• T&M pricing model
• Travel and Expenses factored in
the overall pricing
• Total Contract Value for 19
weeks: USD XXXXX
• The pricing includes warranty
support for 2 weeks
• An effort of 40 hours per resource
per week has been assumed in
computing the cost
COMMERCIALS
OIM Integration with
SAP ECC

2. Scope of Work

3. Scope of Work – Activities In Scope (1 of 2)
Activities In-Scope
 Oracle Access Management integration for SSO of following web applications:
 JIVE
 LMS
 Custom plugin for authentication in OAM, if required
 Customization of OIM functionalities as per Oracle’s recommendations. These may include custom user attributes, custom connectors, custom
adapters, custom approvals etc. However, functionalities like attestation cannot be customized
 User access provisioning/de-provisioning
 Federation for LMS application using SAML
 Remove AD as authentication source for OAM
 Setup OID as central authentication repository for OAM
 Integrate OAM with OID for authentication
 Ecommerce user registration for existing user profiles:
 Retrieve and validate the user profiles for SAP and create them in ATG
 Ecommerce user registration for new user profiles:
 Create the user profile in SAP ECC
 Create the user profile in ATG
 One time user profile cleanup during migration of profiles from AD to OID
 Role and Entitlements configuration in OIM for ecommerce account management

4. Scope of Work – Activities In Scope (2 of 2)
Activities In-Scope
 Integrate Oracle Identity Manager with OID using out of the box
connector
 Integrate Oracle Identity Manager with SAP ECC using out of the box
connector
 Establish real-time sync between AD and OID
 Configure Oracle Identity Manager for approval workflows
 Configure BI Publisher to provide out of box reports provided by
Oracle Identity Manager
 Warranty Support of 2 weeks
 UAT Support
 Go Live / Deployment Support
Testing Activities In-Scope
 Functional Testing
 System Integration Testing
 Localization Testing in 10 languages including English, Chinese,
French, Japanese, Korean, Italian, Spanish, Russian, Portuguese &
German for Central login page, user registration, self service &
migration
 Browser Compatible Testing (Win OS: IE 11, Chrome v52, Firefox
v45, Safari 5.1)
 Mobile / Tablet Testing (iPad Air 2 / IPhone 6 Plus)
 Performance and Scalability Testing for OIM & OAM
 Security Testing (OWASP)
 For security testing self registration module in OIM application and
2 application integrated with OAM (OWASP)

5. Scope of Work – Activities Out of Scope
Activities Out-Of-Scope
 Language Support other than English
 Any content migration apart from AD to OID
 SSO integration of SAP
 Authorization at integrated application end
 Infrastructure/Network setup - OS, FIREWALL, hardware load
balancer, Certificate.
 IWA (Integrated Windows Authentication) – Kerberos based
authentication
 Procurement of any software and hardware licenses for the project.
 Role Mining
Testing Activities Out-Of-Scope
 Content Testing for all the Languages
 Localization Testing for all other languages that are not in-scope
 Compatibility Testing for all other Browsers / devices that are not in-
scope
 Testing of any existing functionality apart from the new features
added in this engagement
 Performance Tuning of Databases
 Penetration Testing
 Mobile Device Security Testing
 Test Data Management
 Test Environment Management

6. Solution Approach

7. ABC’s Proposed Architecture Landscape
Admin
Administration
and reporting
Admin
Administration
and reporting
Oracle Identity Manager
11g R2 PS3
Approval
Role and
Entitlement
Management
Provisioning
Registration
Customers
Oracle Access Manager
11g R2 PS3
Agent Based SSO
Customers
SAML based federation
Webgate
OID
Connector
SAP
LMS
OID
Authentication
Authentication Authorization
Federation
External Users
AD
JIVE
AD
Connector
External Users
ATG
Existing and New
Users
New Users
AD-OID Sync

8. Key Solution Highlights
 Provisioning/De-provisioning user access to following SAP using Oracle Identity Manager
 User profile clean up during migration from AD to OID
 Role and Entitlements management in OIM
 Implementation of Single Sign On functionality for the following Web Applications
 JIVE
 LMS
 Federated SSO for LMS through SAML 2.0 using Oracle Access Manager
 Implementation of multi-level workflow management capability using SOA approval workflows
 Registration of New and Existing user profiles from SAP to ecommerce
 User profile migration from AD to OID

9. Proposed Migration strategy for OIM
implementation
AD OID 2 way Sync
 Deploy Directory Integration Platform (DIP) 11g on
Weblogic Server
 Create a Synchronization Profile with OID as
Destination
 Configure the AD connection details
 Add mapping rules by providing the AD Container DN
and Destination OID Container DN
 Synchronization profile is executed every one
minute (configurable option) via Quartz
scheduler (DIP component)
 Repeat the same by configuring OID as Source and AD
as Destination

10. Engagement Timelines

11. Commercials

12. Resource Load and T&M Cost

13. Monthly Cost

14. Assumptions & Dependencies

15. Key Assumptions & Dependencies (1 of 3)
General
 ABCDE stakeholders will be available to meet with ABC representatives and participate in workshops, discussions as required.
 Designated ABCDE stakeholders will review and sign off on deliverables within agreed upon timeframes.
 ABCDE will designate a single point of contact with whom all project communications will be addressed
 Scope is based on ABC’s understanding of information provided by ABCDE. For any changes discovered during requirement analysis phase, ABC will
revisit estimation/cost
 Any communication to end users will be done by ABCDE
 For any changes to scope/assumptions and/or any delays due to external factors, ABC will revisit estimate/cost
 ABC will require lead time of 4 - 6 weeks to start the project after sign off
 Any changes required for target applications such as Active Directory for integration will be performed by ABCDE
 Product enhancements/issues, if any, will be addressed by respective product vendor
 SSO would be implemented between browser and web gate and identity of the user will be provided to the application though header variables
 All target applications must be available in Dev, Test, production and production DR environments and must be ready for integration
 All application stake holders will be available at the time of requirement analysis
 Single Webgate will be implemented for access management of web interface of scoped applications
 Auditing functionalities will be leveraged using out of the box capabilities of OIM and OAM
 Role management using out of the box Oracle Identity Manager capabilities
 Similar directory structure will be maintained while migrating data from AD to OID
 OID will act as central authentication repository
Technical

16. Key Assumptions & Dependencies (2 of 3)
 OIM will supply role and entitlement information to ATG. User rights management based on roles will be done with in ATG
 Access to development environment must be available on the first week of project initiation and rest of environments as per the schedule before the
installation
 Total user base considered to be 500,000 users
 All auditing and logging will be done using out-of-the-box auditing features
 Only two levels of approval workflows to be integrated when required.
 All hardware must be available before the start of installation (during first week of project initiation)
 All product licenses must be procured before project initiation
 ABC will follow up with Oracle on product issues based on ABCDE-Oracle partnership
Technical
 Login functionality with different User Access are considered for QA scope
 Verification of Existing functionalities is out of scope
 QA will undertake regression testing of In-scope functionalities, while regression testing for existing functionalities are not in scope for QA Team
 Localization Testing to be conducted for only 10 languages - English, Chinese, French, Japanese, Korean, Italian, Spanish, Russian, Portuguese &
German.
 QA (Functional and Performance testing) will be performed on dedicated test environments
Technical-QA

17. Key Assumptions & Dependencies (3 of 3)
 Code freeze happen as per the plan and any new CR will affect the schedule and effort
 Application availability is ensured in Offshore hours for testing without frequent build deployment & environment downtime. Any such occurrence
will affect QA schedule
 UAT is performed by ABCDE and Bug fix support will be provided by QA team as part of UAT support
Technical-QA
 12 Test Scripts/cases covering critical features of IDM have been considered in scope.
 4 Performance Scenarios (Load-2, Scalability-1 & Day-in-Life Performance-1) considered in scope.
 ABCDE will provide the Performance Testing environment similar to production in terms of hardware capacity, software components etc.
 ABCDE will provide the test data setup and test bed setup for executions of batch and online executions and also responsible for managing the
Performance Test environment
 ABCDE will provision Test Machines & provide admin access to machines to install Performance Test Tools and load generators in their environment
for simulating the load
 ABCDE will ensure necessary access to applications, performance monitoring tools and servers will be provided to ABC team to carry out scripting
and execution activities.
 ABCDE will review the test results and observations and will provide the necessary and timely signoff on the deliverables provided by ABC.
 Schedule will re-visited if there is any delay in environment availability
 Availability of sufficient test data volume (similar to live data volumes) and the data for test script creation and execution.
Performance QA

18. Thank You