COmanage Developers List

[Tom Barton <>]

Niels van Dijk wrote:
> Next up the generic webproxy for authenticating and provisioning
> (remote) apps.
> It is often a lot of work to domesticate an application by actually
> changing it, and sometimes even impossible, as in our test case (Adobe
> Connect), when it is a closed source app, or the app lives 'in the
> cloud'. However, a number of apps do have APIs for authentication and/or
> provisioning.
> The basis idea was therefor to have a standardized, configurable
> domestication 'device', in our case an Apache reverse proxy in front of
> the (remote) application. 

Use of reverse proxy for authenticating in some circumstances is clear. 
And you know I like the JIT provisioning approach. I wonder if there may 
also be other approaches, and if you guys discussed any others. For 
example, if a user is first "invited" to the collab platform, any user 
account provisioning might be triggered in that workflow. And when 
someone puts the user into a collab group or removes them from it, that 
event might trigger a corresponding provisioning action.

Thanks,
Tom