{"push_id":2052783599,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"268759cc4d87805d1967e31ac3a22fda7fdad89b","before":"d634b83eb552a3baee966585db8dafe8c5b3ac3c","commits":[{"sha":"268759cc4d87805d1967e31ac3a22fda7fdad89b","author":{"name":"philipp","email":"bee3cf1bf8b3c6cfa92f816fd412ab39c1a824bc@posteo.net"},"message":"removed ident-store in favor of library, created authorization library\n\nstarted to refactore the ident-store to be a library instead of a\nrunning service, so that it can be easily reused and enforces a more\ndistributed style of identystores since it is dependent on kafka anyhow.\n\ncreated an authorization library to start to build an distributed authz\nnetwork based on kafka, the idea is that every secured service can check\nif the user is eligible to use that service by itself. There's is still\nstuff todo like to create an easy abstraction for that service.\n\nNext steps are to build a more sophisticated showing service which is\nsecured. I was thinking about creating a service which is showing all\nlogged in user with access_token. To first user should be registered by\na script directly in kafka than. However, when I've time. Probably never.\n\nThe google authentication service now redirects with the external\nidentifier of that token which will be created by any authz instance.\n\nMaybe it makes sense to build the authz decision (token validation etc)\nas a singleton cluster, but I have to play around it a lot more to come\nto a conclusion. Till than I'll favor lib based cause moving should be\na lot easier than.","distinct":true,"url":"https://api.github.com/repos/nichtsfrei/simple-identity-provider/commits/268759cc4d87805d1967e31ac3a22fda7fdad89b"}]}
{"actor":{"display_login":"nichtsfrei"}}