You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2015/05/29 11:48:17 UTC
[jira] [Commented] (OAK-2652) [Oak API remoting] Finalize http
authentication
[ https://issues.apache.org/jira/browse/OAK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564484#comment-14564484 ]
Francesco Mari commented on OAK-2652:
-------------------------------------
I think that this issue can be closed. The bug regarding the realm is already fixed by the latest patch attached to OAK-2502. We can discuss additional authentication mechanisms and implementation details in narrower issues when the initial implementation of the Remote API will be merged into Oak.
> [Oak API remoting] Finalize http authentication
> -----------------------------------------------
>
> Key: OAK-2652
> URL: https://issues.apache.org/jira/browse/OAK-2652
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: remoting
> Reporter: Fabrice Hong
> Fix For: 1.3.0
>
>
> * In addition to unauthorized status. set response header to "WWW-Authenticate" ="Basic realm=\"Oak\"" in case the user is not authenticated. see class "OakServlet"
> * Implement the other authentication Schemes (Digest, NTLM ?). Use standard libraries for this. Apache ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)