Hi Ingo, The short answer unfortunately is that Allura uses some of the basics of Turbogears but does its own thing for most stuff, including authentication. The authentication system is pluggable in Allura, so it should be possible to write a SAML plugin, but the turbogears extension wouldn't work.
These docs explain the methods that would have to be implemented: https://forge-allura.apache.org/docs/api/lib/plugin.html#allura.lib.plugin.AuthenticationProvider And https://forge-allura.apache.org/p/allura/git/ci/master/tree/Allura/allura/lib/plugin.py has the base AuthenticationProvider and the LocalAuthenticationProvider and LdapAuthenticationProvider code, which could be useful references. -Dave On 12/25/17 1:26 PM, Ingo Hornberger wrote: > Hey guys! > I just did some research how allura could be extended with SSO > functionality. I encountered that OpenID was once supported but > discontinued. > > Then I found out that turbogears itself supports SAML with a pluggable > extension: > > https://pypi.python.org/pypi/tgapp-samlauth/0.0.2 > > This sounded promising from an outside point of view. But I am new to TG, > so I wanted to ask you guys for some hints to find the best and most > pragmatical approach to get SAML or a similar protocol to work. It should > just cooperate with keycloack. So a few configurations are possible, while > SAML would be prefered. > > Could such an extension work in allura, or did you change too much in the > authentification system? > > Thanks in advance! > > Ingo > -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
