[
https://issues.apache.org/jira/browse/KNOX-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143481#comment-15143481
]
Larry McCay commented on KNOX-670:
----------------------------------
I think that #2 is probably sufficient.
This would require similar mechanism as is available for services for certain
routes - correct?
The particular URLs for KnoxSSO with the embedded application would be somewhat
different due to the resource path exposed for the websso API.
"https://localhost:8443/gateway/knoxsso/api/v1/websso";
and the login app would be something more like
"https://localhost:8443/gateway/knoxsso/login/index.html"; - or whatever
Due to the nature of the knoxsso API we can always be sure of that particular
URL - given the host, port and gateway name of course.
Given a mechanism like your option #2, we could define within the application
element the routes to exclude from authentication or the whole pipeline if that
makes sense. I could see some audit adding value but could be convinced
otherwise.
> 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)
