[
https://issues.apache.org/jira/browse/KNOX-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143603#comment-15143603
]
Kevin Minder commented on KNOX-670:
-----------------------------------
Actually this could all possibly be far more powerful/elegant.
Looking back into the crusty old code it turns out that moving to configuration
based services lost us a bit of capability.
It used to be possible for a ServiceDeploymentContributor to define its own
chain on a per url pattern basis.
By convention all of our existing service deployment contributors used the
exact same chain definition for all paths.
Therefore when config based services were introduced that chain was hard wired
for all paths.
What if conf/applications/sample/service.xml (still using the legacy file name)
could look like this:
{code:xml}
<service role="knoxlogin" name="knoxlogin" version="0.0.0">
<chains>
<chain name="insecure">
<provider role="xforwarded"/>
<provider role="rewrite"/>
</chain>
<chains>
<routes>
<route path="/login/**" chain="insecure"/>
<route path="/**"/>
</routes>
</service>
{code}
Any rote that didn't specify a chain would use the "default" chain.
> Knox Should be able to Host Simple Web Apps
> -------------------------------------------
>
> Key: KNOX-670
> URL: https://issues.apache.org/jira/browse/KNOX-670
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Kevin Minder
> Fix For: 0.9.0
>
> Attachments: KNOX-670_001.patch, KNOX-670_002.patch
>
>
> I think that we need the ability to serve up arbitrary web app resources.
> Given a conf/applications along side conf/topologies, we should be able to
> spin up a simple application that can be used as a central login facility
> with KnoxSSO, a management UI or any number of simple applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
