wso2is - Recommendation for integrating WSO2 API Manager, Identity Server and Shibboleth -
what current, recommended way setup wso2 api manager use sso against shibboleth idp?
our organization has existing sso infrastructure built around shibboleth’s idp integrate our api manager installation. ideal use case:
- user navigates api manager store.
- user redirected shibboleth idp login page.
- if 1 doesn’t exist, api manager account created , assigned subscriber role.
- user returned api manager , logged in. “signed-in-as:” renders reasonable user name (i.e. not guid).
i’m aware there included saml2 authenticator component api manager limited in features, not handle encrypted assertions, using specific attributes username/display name , automatic user creation.
i understand write custom authenticator, rather avoid creating code base needs maintained , doesn’t have community support. if simpler solution cannot determined do.
what investigating delegating user management api manager wso2 identity server. delegate authentication shibboleth , auto provision users before returning am. seems address of issues mentioned above.
- firstly, appropriate strategy? if so, how recommended , configured?
- should , both point same jdbc database or should point is’s ldap server?
- regarding authenticator pointed is, should use saml or oauth, or there better/simpler one?
shibboleth idp v2.4 – saml2 attribute push preferred.
wso2 api manager v1.6.0
wso2 identity server v5.0.0
here's results of research, interested:
1) appropriate strategy. new features in 5.0 release of identity server centered around scenario. , 1.7 release of includes features facility setup. i've heard developers intend push integration further in next few releases.
2) of 1.6 there bug made required share same primary jdbc user store. of 1.7 should more open.
there not seem preference people @ wso2 between ldap , jdbc (except default h2 db not designed production environments), if choosing between installing db or open ldap this, ldap server seems more suited choice.
3) it's best use saml communicating between 2 when goal present user un/pw screen. when goal login pre-issued tokens oauth. api manager , use both protocols behind scenes, answer particular question seems saml. in future wso2 plans expand "trusted idp" feature of products, streamline process (and use saml behind scenes).
Comments
Post a Comment