Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support API Token security in REST layer #52

Open
aslakknutsen opened this issue Jun 13, 2013 · 1 comment
Open

Support API Token security in REST layer #52

aslakknutsen opened this issue Jun 13, 2013 · 1 comment
Assignees
@aslakknutsen
Labels
code test

Comments

@aslakknutsen
Copy link
Member

Integrate security with normal REST operations.

GET is open

PUT/POST/DELETE require auth.
Make sure auth is reflected in OPTIONS
@ghost ghost assigned aslakknutsen Aug 15, 2013
aslakknutsen added a commit that referenced this issue Aug 23, 2013
@aslakknutsen
Add Security to StateChanging REST methods
7ae39aa 
* POST, PUT, DELETE now require authentication
* Change to use Twitter Sign In, instead of app authentication
* Workaround AGOVA-53

When the Security Module is included in the deployment
all REST services are locked down. This means any state changing
methods will require authentication. The Security Module test-jar
comes with a Arquillian Extension that will setup do a full
authentication in AfterDeploy and setup RestAssured with a
valid Http Session. This allow the conference, user, attachment
REST Stories used as final functional tests in the Application
to work with our without the Security Module included. The REST
tests have no knowledge of the Security Module.

Issue: #52
aslakknutsen added a commit that referenced this issue Aug 23, 2013
@aslakknutsen
Add Security to StateChanging REST methods
c9ed918 
* POST, PUT, DELETE now require authentication
* Change to use Twitter Sign In, instead of app authentication
* Workaround AGOVA-53

When the Security Module is included in the deployment
all REST services are locked down. This means any state changing
methods will require authentication. The Security Module test-jar
comes with a Arquillian Extension that will setup do a full
authentication in AfterDeploy and setup RestAssured with a
valid Http Session. This allow the conference, user, attachment
REST Stories used as final functional tests in the Application
to work with our without the Security Module included. The REST
tests have no knowledge of the Security Module.

Issue: #52
aslakknutsen added a commit that referenced this issue Aug 25, 2013
@aslakknutsen
Use env variables instead of System Properties
52ea049 
Avoid exposing secret data in logs etc.

Issue: #52
@aslakknutsen
Copy link
Member Author

Delay til 1. rev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aslakknutsen aslakknutsen

Labels
code test
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aslakknutsen