Modern applications are web-based. This provides high flexibility and client independence, but diversity becomes a challenge for end users – especially casual users. How do I login? How do I get files from other applications? A functioning integration goes beyond single sign-on – we at Univention work on this together with software manufacturers and operators and can present initial results.

1. Addressing the contradiction between
modularity and integration
Ingo Steuwer
Univention GmbH

2. Reminder - Vision: Integrated platform
Integration in Univention Portal
●
Seamless user experience
●
Integrated Apps
Interacting Apps
●
Integration between Apps
●
Open, common standards
Individual modules
●
Selectable functionality
●
Integrated & Scalable
Expected functionality
●
Focused functionality
●
Usability, Usability, Usability
Identities

3. Why Integration?
Usability
●
Ease access
●
Reduce complexity in workflows
●
Clear functionality
Functionality
●
Don‘t implement the same
functionality twice
●
Make Benefits of software A
available in software B

4. Why Modularity?
●
Different organizations needs different functionality
●
There is no such thing as „one fits all“
●
Reduce dependencies
●
Increase Performance and Security
→ Organizations need „Freedom of Choice“

5. Integration between Apps – example Usecases (I)
●
Too many places to store files: ERP, CRM, Groupware, DMS, …
→ access one file storage from all Apps
●
Even worse (?) for
●
appointment scheduling / calendars
●
contact management / address books

6. Integration between Apps – example Usecases (II)
●
Initiate communication (Phone, Chat, Mail, Video) from all Apps
●
With the same tool
●
With the same address book
●
One place to edit personal settings – not per application
●
Nickname, profile picture, phone number, ...
●
One place to Search
(tough one...)

7. Areas to work on
Frontend
●
Cross software links / Access to
functionality
●
Remove duplicate functionality
●
Standardized naming
●
Common Look & Feel
Backend
●
Choose & implement open and
common standards
●
Preconfiguration for end users
●
Standardize „resource
identification“

8. Prerequisites – Identity Management
●
Provisioning / Rostering of
Accounts
●
Single Sign On (SSO)
●
SAML and / or OpenID Connect
●
„Ressource directory“ - which
ressources are available for the
current user?
Identities

9. Frontend – Univention Portal
Objectives
●
Overview of available software /
services
●
Individualized view for each user
●
Up to UCS 4.4: stand-alone web
application with SSO
Current Proof of Concept
●
Integration of standard use
cases: change password / Self
Service / edit profile etc.
●
Embedded Apps (currently:
IFrame) – configurable per App
●
Design Cleanup

10. Portal
Screencast
basic
functionality

11. Challenges - Portal
●
Integrated SSO for SAML &
OpenID Connect
●
Usability
●
Integration to be decided per
usecase
●
Limitations of IFrames
●
Security
●
Compatibility
●
Performance

12. Integration PoC: Open-Xchange + ownCloud
Initial Usecase:
An user of OX Appsuite is able to directly access the ownCloud file
storage to store incoming attachments or retrieve files to be attached to
mails or appointments.

13. Screencast
Open-Xchange
& ownCloud
integration

14. Integration Example: Open-Xchange + ownCloud
Findings:
●
Required technology is available, here: WebDav + SSO (OpenID Connect)
●
Seamless Integration needs more „glue“:
●
Harmonize SSO (OX on UCS often uses SAML, Backend SSO with ownCloud
needs OpenID Connect)
●
WebDav implementation no OX upstream component
●
Preconfiguration for end users needed
●
Usability improvements (wording, look&feel)

15. Next Steps
UCS 5.0
●
Integration of UMC in Portal
●
Harmonize Look & Feel
●
Harmonize SSO (SAML + OpenID
Connect)
Integration between Apps
●
Implement the „glue“ for PoC
●
Adopt to further Usecases
●
Adopt to further Apps
●
Standardize
Any participation is welcome!

16. Thank You!
Ingo Steuwer
Univention GmbH