You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/14 21:55:00 UTC

[jira] [Commented] (KNOX-981) Make Topology Instance Available in WebContext for Runtime Access

    [ https://issues.apache.org/jira/browse/KNOX-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088168#comment-16088168 ] 

ASF subversion and git services commented on KNOX-981:
------------------------------------------------------

Commit 54e3a7edd6bea957639215daaa02eb465889a5c6 in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=54e3a7e ]

KNOX-981 - Make Topology Instance Available in WebContext for Runtime Access

> Make Topology Instance Available in WebContext for Runtime Access
> -----------------------------------------------------------------
>
>                 Key: KNOX-981
>                 URL: https://issues.apache.org/jira/browse/KNOX-981
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 0.13.0
>
>
> There are times when access to the topology and the configured services within it is required by an application, service or provider at runtime.
> For instance, we need to be able to check the whitelist expression that is configured in the KnoxSSO service from within the KnoxAuth application. Rather than redundantly configuring it in both places or making a topology specific config item global within gateway-site.xml we should provide access to the topology object itself for all apps, services, providers processing requests within a topology.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)