What if you, in order to facilitate having a login form on every page, built another "tile" for using as a login form on every page where you wanted one. This "tile" would do a secure POST to your actual login form (it would be it's action= value). Then, assuming your CMA login form is not a static page, you could easily get the values for the username/login. You could also populate those values in your form - and auto-submit that form as mentioned before.
Someone *please* stop me if I'm talking foolishness! Thanks! Eddie Eddie Bush wrote: > I guess that still doesn't help the guy that wanted to put a login > form on every page, but it gives you a way to easily invoke CMA and > have control over where it goes. This would permit users to login on > a "let" basis instead of a "have to" basis. I think that's one of the > most stringent requirements in each of our scenarios. It also > involves a lot less rigamaro than other suggestions I've heard (I > think). Of course, it doesn't address auto-login though - but a tidy > piece of javascript should cinche that up. > > Could you map a struts action for the login page? You could populate > something in the request ahead of the form being shown. Then, check > whatever you must when your presentation action is invoked. Then, > check in your login page to see if that information is available. If > it is, output the javascript to handle auto-submission of the login. > If it is not, either do not output/include/whatever the javascript - > or include an "no-op" inplementation of the function that is invoked > by ... whatever invokes it ;-) (onload=?) > > Am I getting warmer or just deluding myself? > > All comments welcome! > > Eddie -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
