Common Redirection Mechanism

794 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
794
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
40
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Common Redirection Mechanism

  1. 1. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Common Redirection Mechanism Author: Roman Agaev Date: Tuesday, March 27, 2007 15
  2. 2. Roman Agaev, M.Sc, PMP Owner, Supra Information Technology ltd. Contents 1 Abstract.......................................................................................................................4 2 Analysis.......................................................................................................................4 3 Design.........................................................................................................................5 4 Conclusion...................................................................................................................5 5 Appendixes..................................................................................................................5 25
  3. 3. Figures Figure 2-1: Redirection mechanism - high level diagram..............................................4
  4. 4. 1Abstract The main goal of this document is trial of giving an additional level of potential client redirection within Siebel application after his/her authentication and primary authorization done using standard authentication adapters/mangers, responsibility and visibility features. The analyzed module must provide: •Additional client side redirection •Additional authorization •Additional redirection logic 2Analysis The module in general must answer on requirement that declares the neediness in some circumstances the client redirection within the Siebel application. •The server side redirection may be achieved using GotoView method of Application global and has no ability to be exposed in different way from within Siebel business layer. •The client side redirection in opposite can be realized using standard Siebel business layer. Within the business layer the ability of inline html/script injection can be used on order to achieve an appropriate redirection. The following diagram describes the system's high level: Figure 2-1: Redirection mechanism - high level diagram
  5. 5. 3Design The functionality can be achieved using Field Retrieval Type property of Siebel applet's control. The values of that property that are relevant for the current discussion are: •Symbolic URL – used just for Siebel web site decomposition inline iframe control (activex solves the problem of window object access) form request – raises new window •Field Value – straight html/script injection1 The design will include several approach adaptation steps: •Common parameters mechanism for html/script storage •Siebel business component – new calculated field with html/JavaScript rounded by quotes •Siebel applet – exposition of previously defined calculated field using Field Retrieval Type populated as Field Value 4Conclusion The approach described in current essay permits another level of authorization and mainly can be used in order to redirect an unauthorized user from sensitive information to the appropriate web page for further authorization process. The implementation is very simple, accumulates several approaches like common system parameters2. 5Appendixes "Workflow usage best practices" (Roman Agaev) "Common VBC paradigm" (Roman Agaev) "Common error handling mechanism" (Roman Agaev) "System parameters paradigm" (Roman Agaev) 1 Document object should be used instead of window object, because of frame complexity within Siebel web site exposition 2 For additional information regarding the topic refer to "System parameters paradigm" from Appendixes section of the document.

×