Federation
Federation is a term that means transferring identity information across two (or more) independent domains. Independent domains are normally governed by separate Identity Providers.
For Ubilogin customers the federation use cases can mean several things and Ubilogin supports many different federation use-cases and set-ups.
For instance, two main use cases for federation can be identified: B2B (also including business-to-government, B2G) and B2C (also including government-to-customer, G2C).
In B2B-Federation there is usually a thrive to achieve role based federation, where the federated identity will deliver role based information to the receiving Identity Provider; and access control decisions are made based on that information. Role based federation does not require user accounts in both domains. It is sufficient to have the user account in the sending domain, which makes it a very attractive way to federate use identities between partners and customers.
B2C-Federation usually means that two or more companies are building value chains for their customers. Services that are offered to the public usually have their own user repositories, which is a valuable asset for any company that wishes to conducts business with the public. B2C-Federation enables these independent service providers to build value chains, where the user can easily move from one service to the next using federated identity. In B2C-Federation separate user accounts can be linked so that the next time the user visits these services, true SSO between the services can be achieved.
A typical value chain for the customer could be a vacation planning, where the user books a flight, reserves a car and books a hotel room using different services. When these services use federation, the user experience is improved and the partner companies can enjoy growing revenues as they enlarge their potential customer base through the partnerships.