The Ometa solution is built on Microsoft SharePoint 2010 and provides in
an intranet and an extranet. By separating intranet and extranet from each
other a maximum security for the internal information within the federation is
guaranteed. The Ometa Integrator Framework enables the proposed integration to
support the publication process and to keep a track record of it. This, by the
way, provides the possibility to simply re-track a publication from the
extranet. With this architecture Ometa combines maximal security with maximal
integration.
Claim
Based Form Authentication
The Ometa solution for Federations is used by
‘internal’ federation employees and ‘external’ federation members. It’s
important that a user gets authenticated during the login. In that way the system
can determine which access will be provided. This is done by means of Claim
Based Form Authentication, a technique that takes combines internal
authentication like Active Directory with an external authentication source.
The
concept of the landingspage
Ometa has built
a solution that presents the personalised data on a landingspage in SharePoint.
All users login on one specific site and depending on the context, only related
sites, working groups and subjects are shown. The latest published documents on
these sites, belonging to the role of the user, shall we shown. All data comes
from a central database which simplifies the maintenance of it.
Identity Access Management
Ometa has built
a solution for Identity Access Management that only one password is needed for
intranet and extranet users. Members that have only access to the extranet are
identified during authentication and their passwords may come from another
authentication provider by which a ‘Single Sign-On’ principle can be supported.
The login takes place via one central page and the selection of the
authentication provider is part of the Ometa solution. This can be defined for each user in
the central database.
Ometa
Integrator Framework
The Ometa Integrator Framework is developed to unlock data from back-end
applications to a SharePoint portal. The power of this framework is provided by
its configuration capabilities via repositories which avoids the creation of
fixed peer to peer connections.
Single Sign-On
Federations often make use of different applications that members get
access to. To improve on the user experience it is crucial that a Single
Sign-on principle can be supported. Indeed, we don’t want to confront members
with multiple login screens. The Ometa Integrator Framework can support this
principle in three different manners:
·
The ‘Profile’
makes usage of a connection that can access an external service that has always
the right to the external application. Mostly used for situations where the
information of the external application is not secured.
·
The ‘Profile’
is configured to make a connection to a specific user of an external
application. Portals or specific functionality within a portal can make use of
specific profiles. This can be considered as a kind of Role Based
Authentication.
The ‘Profile’ is configured
to make a connection with a service which supports authentication tokens which
can be forwarded. In such a way the front office portal user will access the
external application with this own authentication. The external application
need to support this.