[jira] [Created] (KNOX-397) Knox Management API

Larry McCay created KNOX-397: Summary: Knox Management API Key: KNOX-397 URL: https://issues.apache.org/jira/browse/KNOX-397 Project: Apache Knox Issue Type: Bug Components: Server

[jira] [Updated] (KNOX-349) Knox API for Topology Management

[ https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-349: - Issue Type: Sub-task (was: Improvement) Parent: KNOX-397 > Knox API for Topology Management >

[jira] [Created] (KNOX-398) Knox API for Server Info

Larry McCay created KNOX-398: Summary: Knox API for Server Info Key: KNOX-398 URL: https://issues.apache.org/jira/browse/KNOX-398 Project: Apache Knox Issue Type: Sub-task Components: S

[jira] [Commented] (KNOX-398) Knox API for Server Info

[ https://issues.apache.org/jira/browse/KNOX-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039382#comment-14039382 ] Larry McCay commented on KNOX-398: -- Implement this first as it is low hanging fruit and pro

Anonymous API Patterns

All - As I begin to add the beginnings of the management API to Knox, it occurs to me that certain resource URLs will require/allow anonymous access. For instance, admin/api/v1/version shouldn't require authentication - since it may be used to determine which contract to use or some other non-req

[jira] [Commented] (KNOX-398) Knox API for Server Info

[ https://issues.apache.org/jira/browse/KNOX-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039478#comment-14039478 ] ASF subversion and git services commented on KNOX-398: -- Commit d3d269f9

[jira] [Created] (KNOX-399) Allow Anonymous Access to Select API Patterns

Larry McCay created KNOX-399: Summary: Allow Anonymous Access to Select API Patterns Key: KNOX-399 URL: https://issues.apache.org/jira/browse/KNOX-399 Project: Apache Knox Issue Type: Sub-task

[jira] [Commented] (KNOX-398) Knox API for Server Info

[ https://issues.apache.org/jira/browse/KNOX-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039481#comment-14039481 ] Larry McCay commented on KNOX-398: -- Currently, getting the gateway version through this API

[jira] [Resolved] (KNOX-398) Knox API for Server Info

[ https://issues.apache.org/jira/browse/KNOX-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay resolved KNOX-398. -- Resolution: Fixed Initial commit complete. > Knox API for Server Info > > >

Re: Anonymous API Patterns

My first thought is that this is tied up in the issue of removing the filter chain definition from the service contributor. This has been discussed a number of times including as part of https://issues.apache.org/jira/browse/KNOX-177 Note that I no longer really agree with my proposal documented

Re: Anonymous API Patterns

That is exactly what I am describing. I'll have to dig into the jersey handoff in order to understand though I think you are saying that the patterns aren't used to route to any particular filter chain. Not sure I understand that though given the code in the jersey contributor base class - it loop