What have you chosen for your IDM (Identity Management) layer? Maybe UAA for OAuth2 authentication? But might your microservices application also need to cover other security protocols such as SAML and Kerberos? Should we look to get it all in one Identity Management product? Can you get all that out of an IDM and without being tied to its specific quirks - what if you want to change IDM later? This is a session to share experiences from Activiti and projects at Alfresco Software. We'll focus on what we've achieved with Keycloak and what you can expect from it.
- If you only need Oauth2 then you may not need all the features of keycloak/OKTA
- Systems like keycloak offers a lot in handling multiple protocols and out of the box integrations.
- Keycloak can also make the integration code in your apps quite simple and powerful but harder to then integrate with other Oauth2 servers
YOU MAY ALSO LIKE:
Identity Management and Single Sign-on - How Much Flexibility?
Marcello Teodori is IdeaPlane's Technical Architect.
Ryan Dawson is a core member of the Activiti team at Alfresco (https://www.activiti.org/about), helping to drive forward the Activiti open source project. He has spent 10 years working in Java Development scene in London across a variety of industries. Marcello works in Java and front-end since more than 10 years, always in contact with opensource and communities, as coordinator for the Java User Group Milano from 2003 to 2010. Since moving to London, he’s been working for startups of any size and he’s now software architect in Alfresco for Alfresco Process Services, the enterprise BPM suite based on the open source Activiti BPM Engine.