[
https://issues.apache.org/jira/browse/KNOX-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Kellogg updated KNOX-13:
-----------------------------
Issue Type: Improvement (was: Bug)
> Research/define authorization model
> -----------------------------------
>
> Key: KNOX-13
> URL: https://issues.apache.org/jira/browse/KNOX-13
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 0.2.0
> Reporter: Kevin Minder
> Fix For: Future
>
>
> 1. Define a layered authorization policy from the perimeter as high level
> network access to services and how that layers on top of the finer grained
> ACLs at the services
> 2. Exactly what needs to be encoded in the access token - or available by
> resolving it to some context - in order to fulfill the policy enforcement
> needs inside the cluster
> 3. Where ABAC server integrations will occur - I imagine another layered
> approach here: static attributes at the gateway, more dynamic at or near
> enforcement time and service specific attributes at the service perimeter
> 4. Common access policy done across all services - ABAC is probably a good
> way to introduce something new without stepping on toes
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
