> This is all a little kludgy, but maybe someone else can suggest a
better
> way.
I had a similar problem which I solved in a different way. I think your
solution is better than mine, but here's what I did anyway:
I solved the problem by intercepting the browser redirection between
authentication and validation. I altered the cosign configuration so
that the validation URL for a service was changed from something like:
https://webapp.domain.edu/cosign/valid
to something like:
https://messageapp.domain.edu?https://webapp.domain.edu/cosign/valid
The service at messageapp.domain.edu (itself a cosign webapp) looks at
the users identity and decides what messages to display, and eventually
forwards the browser on to the "real" webapp.
Steve.
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
