Hi Antoine, Thanks for your reply, also on this OpenID Connect subject.
There is a small wordpress addon that does exactly that: https://github.com/daggerhart/openid-connect-generic The only things you needed to configure it, are your own OpenID Connect server specifics, such as issuer, authorization_endpoint, token_endpoint, etc, etc. And those are usually in the docs of whatever product you like. Using that plugin, it was actually very easy to configure wordpress against the keycloak openid connect. (in fact: MUCH easier than SAML!) But I will try if I can concoct a keycloak-specific new source myself, as we have sponsored quite some projects lately, and our funding is not endless... ;-) MJ On 1-5-2017 20:26, Antoine Amacher wrote: > Hello MJ, > > We do not have a 'generic' OAuth2 source, as each OAuth2 has is own API, > parameters to authorize, get the token are different, sometimes it > require a scope, sometimes a token parameter, sometimes none. > > Create a new OAuth source is not too complicated if we have a test > account and adequate documentation, but will require a bit of code. I do > like the idea of generic, but I am not sure it will be that generic > because of arguments stated earlier. > > The best option here seems to develop a new source for Keycloak OpenID, > unless we rework the way how OAuth2 sources are coded. > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
