Hi Peter, >From my knowledge your second idea should be doable with as a "quick n dirty" solution.
As you are already aware when a user hits command?login with successful credentials a session key is returned, this session key is stored within a cookie and passed with every command. Along with this a JSESSIONID is generated. Assuming you can capture this data(SessionKey and JSESSIONID) and create a cookie valid for your management servers domain prior to the user accessing the UI they will be greeted with the dashboard instead of the login page. Hope this is of use, Ian On 28 October 2013 13:11, Erdősi Péter <[email protected]> wrote: > Dear, > > I thinking about a "quick n' dirty" ~SSO solution. > First idea is, to make user capable to reach a page after auth, which can > create new user trought api. > This concept looks workable, but it's really dirty :) > > Another idea is, to make users capable to login via url request. > If i open this url, I can see loginresponse, and my session key: > client/api?command=login&**username=admin&password=** > PASSW0RD&domain=%2F&response=**json > > Are there any way, to use this info (session key practically) to jump the > login page? > > Thanks: > Peter > > > > 2013.10.21. 19:27 keltezéssel, Erdősi Péter írta: > > Dear, >> >> Does anyone know about working shibboleth authentication in ACS (4.2)? >> >> Thanks, >> Peter >> >> >
