The limiting factor is generally time - various aspects of the current
system are clumsy, but they work, so unless someone is particularly
keen and willing to work through all the factors that led to the
current setup and propose changes (including at least a rough concept
of how ongoing maintenance will work), the status quo wins by default.
On 4 September 2014 15:45, Shorya Raj <rajshorya@gmail.com> wrote:Many SaaS solution assume the use of specific centralised identity
> Also, have you considered using Travis? It would allow us to add to the
> configurations, at least generally...
providers, which isn't a function we're prepared to outsource (we know
we need to fix our current proliferation of identity silos, but that's
a big project and there are other tasks ahead of it on the todo list
for the existing infrastructure team).
The limiting factor is generally time - various aspects of the current
system are clumsy, but they work, so unless someone is particularly
keen and willing to work through all the factors that led to the
current setup and propose changes (including at least a rough concept
of how ongoing maintenance will work), the status quo wins by default.