🌌 Digital identities journey w. Neo4J

adriens - May 9 '23 - - Dev Community

❔ About

More and more, as digtialization spreads in our organizations, the importance of digital identities becomes every day more crucial for many reasons.

If you add the fact that we rely on hybrid platforms (SaaS & onPrem) and services, at a point in time, you will need to know what a digital identity looks like for :

  • πŸ›‘οΈ Security (access management, Active Directory,...) governance
  • πŸ’Έ Licences management
  • πŸ§‘β€πŸ’Ό HR knowledge (management, roles, peoples skills balance, prevent mental health issues,...)
  • ☁️ Third party cloud platforms (eLearning, GitHub, Kaggle, Onlineformapro,...)

πŸ‘‰ This post is about showing how we implemented this as a data-driven solution with Neo4J and code to answer complex question on our digitalization journey.

πŸ—ΊοΈ Digital identity... the data way

To discover what digital entities (current state of the art), we query our Neo4J instance's data with introspection like follows with apoc.meta.subGraph:

CALL apoc.meta.subGraph({
  includeLabels: ["Person",
                  "GhMember",
                  "KaggleMember",
                  "OnlineFormaProUser",
                  "DevToAccount",
                  "SumoAgent",
                  "UO",
                  "CigrefJob"],
  includeRels: []
});
Enter fullscreen mode Exit fullscreen mode

Image description

Now, enought talk, let's see how it looks.

πŸ“˜ The digital identity metagraph

πŸ§‘β€πŸ€β€πŸ§‘ Browse identities & people

πŸ”– Related resources

I hope you enjoyed this content and found inspiration.

For more about our data journey, just watch the dedicated speak at #NODES22 :

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .