I would like to provide some insight into Fedlet in today’s post. I will cover the following fedlet related topics in the near future.
To understand the federation concepts such as Identity Provider, Service Provider, Circle of Trust etc., check this post.
What is a Fedlet?
Oracle OpenSSO Fedlet (Fedlet) is a compact, easy to deploy SAMLv2 Service Provider implementation. It includes a small software package and a simple file-based configuration, embeddable into a Service Provider’s Java EE or .NET application.
Where does other vendor federation product defeats Fedlet?
The other vendor federation products such as Tivoli, Oracle etc., defeats Fedlet on some features which is eventually turned out to be tradeoffs for Fedlet and here they are:
What are the key features covered in Fedlet?
Fedlet typically is deployed as a Service Provider in common scenarios. Each service provider requires a fedlet instance. Fedlet acting as service provider can communicate with Single IDP or multiple identity providers. A simple diagram is provided in below screenshot where Fedlet communicates with multiple identity providers.
Fedlet can be deployed in 3 ways:
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com