{"action":"created","issue":{"url":"https://api.github.com/repos/dropwizard/dropwizard/issues/1050","labels_url":"https://api.github.com/repos/dropwizard/dropwizard/issues/1050/labels{/name}","comments_url":"https://api.github.com/repos/dropwizard/dropwizard/issues/1050/comments","events_url":"https://api.github.com/repos/dropwizard/dropwizard/issues/1050/events","html_url":"https://github.com/dropwizard/dropwizard/issues/1050","id":76752093,"number":1050,"title":"Allow \"either-or\" authentication methods for resources","user":{"login":"alph486","id":1747773,"avatar_url":"https://avatars.githubusercontent.com/u/1747773?v=3","gravatar_id":"","url":"https://api.github.com/users/alph486","html_url":"https://github.com/alph486","followers_url":"https://api.github.com/users/alph486/followers","following_url":"https://api.github.com/users/alph486/following{/other_user}","gists_url":"https://api.github.com/users/alph486/gists{/gist_id}","starred_url":"https://api.github.com/users/alph486/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alph486/subscriptions","organizations_url":"https://api.github.com/users/alph486/orgs","repos_url":"https://api.github.com/users/alph486/repos","events_url":"https://api.github.com/users/alph486/events{/privacy}","received_events_url":"https://api.github.com/users/alph486/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-15T14:57:17Z","updated_at":"2015-11-26T22:20:04Z","closed_at":null,"body":"This is more of a question about functionality:\r\n\r\nRight now one can implement a ChainedAuthenticationFactory and have *all* of the auth methods apply. In order to get different authentication behavior for different resources, I guess I would need to break out the resources requiring separate authentication methods into a separate service.\r\n\r\nMy situation, where I believe it would be necessary, is in my OAuth 2.0 based services, my authorization service is in the same deployable artifact as the other resources that will use the tokens vended by it. A user would call /auth/token with Basic Auth and then call /users with Bearer Token auth.\r\n\r\nAny issue with this idea? Is there a way to do this already I'm not aware of?"},"comment":{"url":"https://api.github.com/repos/dropwizard/dropwizard/issues/comments/159999479","html_url":"https://github.com/dropwizard/dropwizard/issues/1050#issuecomment-159999479","issue_url":"https://api.github.com/repos/dropwizard/dropwizard/issues/1050","id":159999479,"user":{"login":"vvondra","id":101691,"avatar_url":"https://avatars.githubusercontent.com/u/101691?v=3","gravatar_id":"","url":"https://api.github.com/users/vvondra","html_url":"https://github.com/vvondra","followers_url":"https://api.github.com/users/vvondra/followers","following_url":"https://api.github.com/users/vvondra/following{/other_user}","gists_url":"https://api.github.com/users/vvondra/gists{/gist_id}","starred_url":"https://api.github.com/users/vvondra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vvondra/subscriptions","organizations_url":"https://api.github.com/users/vvondra/orgs","repos_url":"https://api.github.com/users/vvondra/repos","events_url":"https://api.github.com/users/vvondra/events{/privacy}","received_events_url":"https://api.github.com/users/vvondra/received_events","type":"User","site_admin":false},"created_at":"2015-11-26T22:20:04Z","updated_at":"2015-11-26T22:20:04Z","body":"@alph486 we're exactly hitting the OAuth token case. What was the path you chose to go?\r\n\r\nNot being able to configure the AuthenticationFactory per resource seems like a big limitation to us."}}