java - Single instance of PicketLink for multiple applications -


my intention implement picketlink similar atlassian has done in crowd.

in more detail, want single picketlink instance provide authentication, authorization, sso , idm services multiple java ee applications. point here have single place jpa/ldap configuration, custom idm model , custom authenticators (all above shared between client applications).

as far i've learned documentation, picketlink doesn't offer out of box. imagine client applications using picketlink apis, actual calls being proxied master picketlink instance via rmi/hessian/rest etc. appreciate expert opinion on whether architecture viable, other criticisms , suggestions.

you looking saml

saml xml-based, open-standard data format exchanging authentication , authorization data between parties, in particular, between identity provider , service provider.

picketlink supports saml

you can create picktlink instance (basically javaee app) acts identity provider. instance " ... single place jpa/ldap configuration, custom idm model , custom authenticators ". other javaee applications act service providers. these apps can consume saml-based identity service provided identity provider:

saml

some remarks:

  • there open source or proprietary identity providers can use shibboleth
  • saml uses http underlying protocol
  • saml more or less universal. kinds of technologies can use saml. not limited java.
  • from security standpoint it's better use well-known, well-established technologies instead of writing own. saml well-known. writing own identity provider risky.

Comments

Popular posts from this blog

angularjs - ADAL JS Angular- WebAPI add a new role claim to the token -

php - CakePHP HttpSockets send array of paramms -

node.js - Using Node without global install -