keycloak-scim/topics/identity-broker.adoc

30 lines
1.5 KiB
Text
Raw Normal View History

[[_identity_broker]]
2016-05-25 15:08:14 +00:00
== Identity Brokering
2016-04-18 15:15:25 +00:00
An Identity Broker is an intermediary service that connects multiple service providers with different identity providers.
2016-05-26 16:09:04 +00:00
As an intermediary service, the identity broker is responsible for creating
a trust relationship with an external identity provider in order to use its identities to access internal services exposed by service providers.
2016-04-18 15:15:25 +00:00
From a user perspective, an identity broker provides a user-centric and centralized way to manage identities across different security
domains or realms. An existing account can be linked with one or more identities from different identity providers or even created
2016-05-26 16:09:04 +00:00
based on the identity information obtained from them.
2016-04-18 15:15:25 +00:00
2016-05-26 16:09:04 +00:00
An identity provider is usually based on a specific protocol that is used to authenticate and communicate authentication and authorization information to their users.
It can be a social provider such as Facebook, Google or Twitter. It can be a business partner whose users need to access your services. Or it an be a cloud-based identity
2016-05-26 16:09:04 +00:00
service that you want to integrate with.
2016-04-18 15:15:25 +00:00
Usually, identity providers are based on the following protocols:
* `SAML v2.0`
* `OpenID Connect v1.0`
* `OAuth v2.0`
2016-04-18 15:15:25 +00:00
2016-05-26 16:09:04 +00:00
In the next sections we'll see how to configure and use {{book.project.name}} as an identity broker, covering some important aspects such as:
2016-04-18 15:15:25 +00:00
* `Social Authentication`
* `OpenID Connect v1.0 Brokering`
* `SAML v2.0 Brokering`
* `Identity Federation`