Skip to content
This repository has been archived by the owner on Jul 3, 2020. It is now read-only.

Implement with Jersey / Guice #72

Open
matt-major-zz opened this issue Feb 18, 2015 · 1 comment
Open

Implement with Jersey / Guice #72

matt-major-zz opened this issue Feb 18, 2015 · 1 comment

Comments

@matt-major-zz
Copy link

I'm interested in using the OAuth-APis to protect endpoints in my Jersey/Guice project.

I will run the standalone Authorisation Server and I would like to use the AuthorizationServerFilter within my application.

Is any able to elaborate on how I could do this? Is it possible that I can then protect endpoints with the @RolesAllowed annotation?

@gvanderploeg
Copy link
Contributor

Hi Matt,

Glad to hear you're about to use Apis.
The resource-server side of things is pretty straightforward with the AuthorizationServerFilter, you will probably get that right quickly.

Setting up the Authorization Server might be a bit more complex, as you have to make some decisions there:

  • What kind of authentication to use? (integration with an existing system probably? Or simply the username/password auth that's provided (albeit without proper backend store)
  • How and where to deploy it
  • Initialization of some key values in apis.application.properties

The Readme.md already contains a lot of pointers though.
I suggest you just start setting it up using the Readme, and please come back here if you have specific questions.

About @RolesAllowed: this is not supported currently.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants