This section provides information for administrators or developers who are asked to develop mobile applications that use sensitive or confidential content, to which their roles do not allow access. For example, suppose you are a Studio developer for an executive portal and your assignment is to create a new application that shows projected financial results for the next quarter. You know that only one group of portal users (financial officers) is allowed to see this information, and that your role does not permit you to see the application content.First, build a new application based upon some dummy data of the right general format (for example, a PDF document). Actual content replaces this data when the application is deployed to the production system.
Next, assign the correct role to protect this application. You need not know the UA role that will be used on the production portal. In Mobile Web Studio, select Manage | Users/Roles to see if any existing roles meet your needs. If not, create a new role (for example, CFO). The next time you log in to Mobile Web Studio, you have that role.
Finally, create the application with the dummy data, assign the CFO role to it, and save it. At this point, if you have not created the CFO role mapping to a role you do have, the application disappears from your view in Mobile Web Studio. Assuming you do have the appropriate role, you continue with testing, debugging, and so on, and eventually export the content and send it to the administrator to import into the production portal.
When the application is imported to the production portal, the administrator creates the correct mapping of the J2EE role reference CFO to the actual FinancialOfficer security role.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
