Geek Answers Handbook

What is the difference between Shibboleth, WSO2 and Identity Server?

I need to implement Identity Server for our organization and try to figure out the various options available. Demand

  • A single IdP to which other IdPs can communicate and provide authentication / authorization. For example, connect to ADFS of another organization or create an auth database of another org through an endpoint?
  • Single Sign-On (SSO) for users accessing the system.
  • Should work in different organizations - allow other organizations access to a limited resource, trusting their IdP and tokens issued by them.
  • User and role management through the user interface

I narrowed below three

  • Shibboleth - I understand this only on the basis of SAML 2.0, does not support JWT, so it may not work with all clients. I'm not sure that I can communicate with other providers, such as ADFS and receive tokens from there.
  • WSO2 . This supports both SAML and JWT. May refer to other providers for federation.
  • Thinktecture IdentityServer 3.0 is the newest kid in the block, designed as Katana middleware and highly customizable with code.

Can you tell me which one will be more suitable, the pros / cons of each regarding requirements? Are there any specific differences that I need to consider (except for the first two, which are OOTB solutions, and the third, the nuget package, which must be configured in the code)?

+4
1

, , , , , . . , WSO2 Identity Server - , . .

Shibboleth JWT, , , . Thinktecture IS . WSO2 IS, , , WSO2Carbon. , . , . , , . documentation, - . , , WSO2 IS.

, , .

0

More articles:


All Articles