Handling security, multi-tenancy, and self-service reporting for your data as a feature app.
This workshop series features a brand-new demo application—created by the TIBCO Jaspersoft team and projekt202—that illustrates and teaches you how to create answer-generating applications of your own. Over the course of 5 webinars, we will introduce you to the what and the why of data as a feature applications and how you can build your own.
Topics covered in this session:
- Ways to visualize data with Jaspersoft
- Developing a visualization template
- Customizing charts using styles & chart properties
- Creating expressions and data functions
- Using data for non-Jaspersoft visualizations
BATTLEFIELD ORM: TIPS, TACTICS AND STRATEGIES FOR CONQUERING YOUR DATABASE
Managing the Experience + Ad Hoc Reporting
1. Managing the Experience +
Ad Hoc Reporting
(Part 5 / 5) Data as a Feature webinar series
Defining security and delivering self-service
BI in an application
3. 3
Hello from the project team!
3
Rachael Ross
Solutions Architect, projekt202
Seattle, WA
Crystal Phiripes
Program Manager, projekt202
Dallas area, TX
Sherman Wood
Director Solution Consulting WW, TIBCO
San Francisco, CA
Xavier Harrell
Sr. Experience Designer, projekt202
Dallas area, TX
Shane Swiderek
Product Marketing Manager, TIBCO
San Francisco, CA
Chad Lumley
Senior UI Developer, projekt202
Seattle, WA
4. 4
Agenda
4
Intro to security &
embedded BI
How is security
implemented in demo
app?
How is self-service
reporting delivered in
demo app?
Key takeaways
& best practices
9. 9
Agenda
9
Intro to security &
embedded BI
How is security
implemented in demo
app?
How is self-service
reporting delivered in
demo app?
Key takeaways
& best practices
10. 10
Security Design: Different experiences
Manager Driver
Franchise
● People belong in a franchise
● Managers can see data across all
regions in their franchise
● Drivers belong to a region and
can only see their routes
● Managers have self service
● Drivers can only consume
11. 11
Security Implementation in Bikeshare
● Token based single sign on
● Data level filtering in reports/visualizations
● Tenant/Role based access to JasperReports Server resources
● Security rules in domain
Let’s see it!!!
12. 12
Agenda
12
Intro to security &
embedded BI
How is security
implemented in demo
app?
How is self-service
reporting delivered in
demo app?
Key takeaways
& best practices
13. 13
Self Service with Ad hoc
● People belong in a franchise
● Managers can see data across all
regions in their franchise
● Drivers belong to a region and
can only see their routes
● Managers have self service
● Drivers can only consume
15. 15
Agenda
15
Intro to security &
embedded BI
How is security
implemented in demo
app?
How is self-service
reporting delivered in
demo app?
Key takeaways
& best practices
16. 16
Key Takeaways
16
Get complimentary
eBook from
Jaspersoft.com
• Define your security requirements from an end
audience perspective
• Define the user profile to support the requirements
• Domains are the most flexible way to deliver self
service
• Implement security rules in domains to support self
service
17. 17
Get involved with the demo app
17
“How we built it” webinar
series
*Ongoing
Workshops and
documentation
*Available now on Jaspersoft Community!
Guided demo app for on-
demand consumption
*Available on Jaspersoft.com
Access to source code for app
and dataset
* Available on Jaspersoft BikeShare GitHub repo
19. 19
Report repository layout
Public Folder – Canned
Private User or Customer Folders – Custom
Customer 1 Folder
User or Customer 1
User or Customer 2
Customer 2 Folder
22. 22
FOR SHERMAN
SCREENSHOTS & ICONS FROM DEMO APP:
https://drive.google.com/open?id=1U54kljAbH7YIPyw1yQHZiveRSMKPD6WK
PICS OF USERS:
TIBCO ICON LIBRARY:
https://drive.google.com/open?id=0B0t8IoRPE6meZGtNZjJGN0RJa1E
23. 23
● Intro to security and embedded BI
○ Goals (security + personalization)
○ How do you achieve goals?
■ Determine security rules (desired access level for users / customers)
■ Define audience and data related to that audience
■ What visualizations are seen? How are security rules implemented in those
visualizations
■ How are users identified?
● How is security implemented in bikeshare?
○ SSO (when a user logs in)
○ Report level security (reference roles, attributes, permissions of report)
○ Ad hoc / Domains
● Authoring content
● Embedding in app
○ Self-service security features
Working agenda