the idea of a direct login configuration database is raised quite
regularly on this group.
The convenience of having a central repository of up to date
configurations sounds really promising, but when you start looking
into the details a few concerns make the whole idea less than optimal.
- accessing a central configuration repository from within the
application, will leek which sites you are accessing using a direct
login; probably not a big issue if this is a Google account, but I
think it would be very easy for anybody to list some sites you are not
willing to be related to, starting from bank accounts, in order to
avoid highly targeted phishing attacks.
- internet is a huge place to classify, and it also highly mutable.
Keeping a central repository of direct login configurations is going
to be a never ending task. And even if you would start it, a manual
configuration gathering should always be necessary for all the sites
that have not being included yet. All these options would make the
process of configuring a direct login much more complex (given all the
possible paths that should be managed) to implement, to describe, and
possibly to use too.
For these reasons, each time we have looked into how to simplify the
configuration of the direct logins, we have settled for the current
solution. We are planning to streamline the interaction during the
creation of a direct login, but leaving the process mostly unchanged.
I hope you could agree with our vision on this subject.
Best regards,
Giulio Cesare