Initial Focus
The initial focus for mVb is to have this WAYF support the integrated federated system environment assumption of mVb. This can mostly be done through the UI in source:trunk/config.php and source:trunk/language.php files as it's a conceptual change rather than a functional one.
Some thoughts on "login service" versus "wayf"
Is it appropriate to consider this as a login service? The session state really isn't maintained by the wayf tool. The wayf can be considered the ui component/hook for the login transaction, though. The login state is maintained by the mVb external Shibboleth SP protecting the SSO service. It's remembered by the cookies it sets and the policies defined in the SP configuration.
We want to be able to report on the login state to users. This could be done by creating a simple "status" page protected by the same SP configuration that the SSO is protected, something along the lines of how Pubcookie reports the status of your login session if it is invoked outside the context of a login request (ie. directly vs. redirect).
I prefer this being considered the login application since it's the closest thing to username/pass prompting in the Shibboleth context and the Shib code can be viewed more like system infrastructure code that login "calls" and relies on.
