[
https://issues.jboss.org/browse/GTNSSO-32?page=com.atlassian.jira.plugin....
]
Marek Posolda commented on GTNSSO-32:
-------------------------------------
Using of extensible filter is something i looked at couple of years ago, when working on
it. Thing is that ExtensibleFilter is part of GateIn portal codebase:
https://github.com/gatein/gatein-portal/tree/master/component/web/api/src...
and gatein-sso doesn't have dependency on it. Maybe decoupling it to kernel/core would
help? Or maybe easiest is just to create subclass of SSODelegateFilter in gatein-portal,
which would implement org.exoplatform.web.filter.Filter interface? But btv. there is also
filter ordering to care about. AFAIK GenericFilter is triggered as the last filter in the
filter stack when SSODelegateFilter is triggered earlier AFAIR (but maybe it's not an
issue, can't remember now...)
Convert SSODelegateFilter to be an extensible filter
----------------------------------------------------
Key: GTNSSO-32
URL:
https://issues.jboss.org/browse/GTNSSO-32
Project: GateIn SSO
Issue Type: Enhancement
Reporter: Tuyen Nguyen The
Assignee: Marek Posolda
Currently, SSODelegateFilter is declared in web.xml of portal.war. It requires us have to
delivery sso-integration with gatein by default. But they is not always used.
We should decouple it from gatein by using extension filter and we will be able to choice
delivery sso with gatein by default or not.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)