Feb 25th, 2013, 04:48 PM
UAA alone, or UAA and LoginServer
So, should we just consider the uaa only for OAuth requests, and login server for username/password authentication, and as two separate applications.
Or can we still just use uaa by itself and use the URIs for username/password authentication with its ui?
Right now I just have the uaa deployed and when I go to the /login url in my browser, I don't get the js or css files, so just the text and textfields show on white and not pretty. But I also see the message
"If you are reading this you are probably in the wrong place because the UAA does not support a branded UI out of the box. To login to cloudfoundry.com click here. If you were re-directed here by another application, please contact the owner of that application and tell them to use the Login Server as UI entry point."
So that message seems to say to me that I need to run both the uaa as one web app and the login server as another web app.
And one last other question regarding the login server. Does it include URI/REST addresses for username/password login via our own web application?