Use of spring security for multi-user data sources on multiple login pages

The processing of the spring Security multi-login page expands the entrypoint on the Internet, but the policy bean does not exist in version 3.1, so I don't know how to write it, I saw the point code and didn't find these things .. I have such a requirement that a site has administrator login and member login. The two are not verified by a database, the first way to think of this is to judge the identity of the login user based on the hidden domain parameter value on the login page in userdetailsservice. Unfortunately, for such a parameter, it can be obtained in the filter, but it cannot be stored in userdetailsservice. If it is around, you can splice it with username and click "Remove" in userdetailsservice to solve the problem ..

 

However, there are different error pages for Logon errors on different login pages, and different success pages for Logon success .. What about these ..

Spring security does not really consider so many application scenarios ..