I would like to configure the @RequestMapping of ProviderSignInController and ConnectController. The defaults seem to be to "/connect" and "/signin", but I would like to use a different path (e.g., "/social/connect" or "/auth/connect"). My use-case is that my site has usernames URL's that utilize the first path location to represent a profile page for a particular user (e.g., http://www.example.com/username will resolve to a user profile page for the user with username of "username").
As currently written, Spring Social collides with the username "connect" and "signin". It is preferable for me to choose a few reserved word-paths (like, "social" or "auth") and prohibit these as usernames, and and allow server-side flow functionality via these reserved URL's. In this way, I only need to reserve a few URL's. For example, the connect flow could travel through "http://www.example.com/auth/connect" which would leave the "connect" username available for use.
All in all, my use-case is the preservation of username URL address space. Spring Social isn't the only plugin/addon that will require special path treatment.
For more details concerning the background of this comment, see my original question here: