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

SecuredAction ajaxCall replacement #538

Closed
sejkorat opened this issue Mar 25, 2015 · 2 comments
Closed

SecuredAction ajaxCall replacement #538

sejkorat opened this issue Mar 25, 2015 · 2 comments

Comments

@sejkorat
Copy link

Hi Jaliss,

Is there any replacement in the latest version for ajaxCall property? I would get status 401 when I call SecuredAction from ajax.

Thanks,
Tomas
@hohl
Copy link

hohl commented May 25, 2015

vote up, would need that too

@jaliss
Copy link
Owner

jaliss commented Oct 29, 2015

SecuredAction uses content negotiation now. See the notAuthenticatedResult and notAuthorizedResult in the SecureSocial trait for Scala. For the Java API there's a responses parameter in the SecuredAction annotation that takes care of that (see the SecuredActionResponses interface too)

@jaliss jaliss closed this as completed Oct 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hohl @jaliss @sejkorat